SEND_CODE_UNAVAILABLE
SEND_CODE_UNAVAILABLE
Section titled “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).
Error details
Section titled “Error details”- code: 406
- parameterized: no
- mapped methods:
auth.resendCode
Python error class
Section titled “Python error class”from miniproto.errors import SendCodeUnavailablePublic access: miniproto.errors.SendCodeUnavailable.
Provenance
Section titled “Provenance”- layer: 228
- structural source:
tdlib - RPC error source: https://core.telegram.org/api/errors
- 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
miniprotoFast paths where they count. Explicit boundaries everywhere else.