auth.resendCode
auth.resendCode
Section titled “auth.resendCode”No description provided by the pinned schema.
Signature
Section titled “Signature”auth.resendCode#cae47523 flags:# phone_number:string phone_code_hash:string reason:flags.0?string = auth.SentCode;Result type
Section titled “Result type”auth.SentCode
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| phone_number | string | — | — | No description provided by the pinned schema. |
| phone_code_hash | string | — | — | No description provided by the pinned schema. |
| reason | flags.0?string | flags.0 | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| reason | 0 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import AuthResendCodePublic access: miniproto.raw.functions.AuthResendCode.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import AuthResendCode
# Naming the raw request class is local only; it performs no I/O or network request.request_type = AuthResendCodeResult family
Section titled “Result family”RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | BUSINESS_CONNECTION_NOT_ALLOWED | This method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we’re a user, and users cannot invoke methods over a business connection; (2) we’re a bot, but business mode was disabled in @botfather or (3); we’re a bot, but this method cannot be invoked over a business connection. |
| 400 | EMAIL_INSTALL_MISSING | Attempting to send a code to the recovery email, but no email is configured. |
| 400 | PHONE_CODE_EMPTY | phone_code is missing. |
| 400 | PHONE_CODE_EXPIRED | The phone code you provided has expired. |
| 400 | PHONE_CODE_HASH_EMPTY | phone_code_hash is missing. |
| 400 | PHONE_NUMBER_INVALID | The phone number is invalid. |
| 406 | PHONE_NUMBER_INVALID | The phone number is invalid. |
| 406 | SEND_CODE_UNAVAILABLE | Returned when all available options for this type of number were already used (e.g. flash-call, then SMS, then this error might be returned to trigger a second resend). |
Accepted types
Section titled “Accepted types”No non-primitive type relationships were found.
Returned types
Section titled “Returned types”auth.SentCode
Known selected constructors: auth.sentCode, auth.sentCodePaymentRequired, auth.sentCodeSuccess
Related methods
Section titled “Related methods”account.sendChangePhoneCode, account.sendConfirmPhoneCode, account.sendVerifyPhoneCode, auth.checkPaidAuth, auth.resetLoginEmail, auth.sendCode
Availability evidence
Section titled “Availability evidence”- unauthenticated allowed
- user only
Provenance
Section titled “Provenance”- layer: 228
- structural source:
tdlib - canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 228 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.
Source-diff notes
Section titled “Source-diff notes”- tdlib_vs_core: changed_count=68; core_only_count=1; overlap_count=2302; tdlib_only_count=158
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2448; tdesktop_only=null; tdlib_only=accessPointRule, ephemeral.editMessage, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret, updateEphemeralBotCallbackQuery