account.verifyEmail
account.verifyEmail
Section titled “account.verifyEmail”No description provided by the pinned schema.
Signature
Section titled “Signature”account.verifyEmail#032da4cf purpose:EmailVerifyPurpose verification:EmailVerification = account.EmailVerified;Result type
Section titled “Result type”account.EmailVerified
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| purpose | EmailVerifyPurpose | — | — | No description provided by the pinned schema. |
| verification | EmailVerification | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import AccountVerifyEmailPublic access: miniproto.raw.functions.AccountVerifyEmail.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import AccountVerifyEmail
# Naming the raw request class is local only; it performs no I/O or network request.request_type = AccountVerifyEmailResult 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 | CODE_INVALID | Code invalid. |
| 400 | EMAIL_INVALID | The specified email is invalid. |
| 400 | EMAIL_NOT_ALLOWED | The specified email cannot be used to complete the operation. |
| 400 | EMAIL_VERIFY_EXPIRED | The verification email has expired. |
| 400 | PHONE_CODE_EXPIRED | The phone code you provided has expired. |
| 400 | PHONE_NUMBER_INVALID | The phone number is invalid. |
Accepted types
Section titled “Accepted types”EmailVerification, EmailVerifyPurpose
Known selected constructors: emailVerificationApple, emailVerificationCode, emailVerificationGoogle, emailVerifyPurposeLoginChange, emailVerifyPurposeLoginSetup, emailVerifyPurposePassport
Returned types
Section titled “Returned types”account.EmailVerified
Known selected constructors: account.emailVerified, account.emailVerifiedLogin
Related methods
Section titled “Related methods”account.sendVerifyEmailCode, auth.signIn
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
miniprotoFast paths where they count. Explicit boundaries everywhere else.