auth.exportLoginToken
auth.exportLoginToken
Section titled “auth.exportLoginToken”No description provided by the pinned schema.
Signature
Section titled “Signature”auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;Result type
Section titled “Result type”auth.LoginToken
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| api_id | int | — | — | No description provided by the pinned schema. |
| api_hash | string | — | — | No description provided by the pinned schema. |
| except_ids | Vector | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import AuthExportLoginTokenPublic access: miniproto.raw.functions.AuthExportLoginToken.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import AuthExportLoginToken
# Naming the raw request class is local only; it performs no I/O or network request.request_type = AuthExportLoginTokenResult family
Section titled “Result family”RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | API_ID_INVALID | API ID invalid. |
| 400 | API_ID_PUBLISHED_FLOOD | This API id was published somewhere, you can’t use it now. |
| 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. |
| 500 | AUTH_RESTART | Restart the authorization process. |
Accepted types
Section titled “Accepted types”No non-primitive type relationships were found.
Returned types
Section titled “Returned types”auth.LoginToken
Known selected constructors: auth.loginToken, auth.loginTokenMigrateTo, auth.loginTokenSuccess
Related methods
Section titled “Related methods”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