auth.finishPasskeyLogin
auth.finishPasskeyLogin
Section titled “auth.finishPasskeyLogin”No description provided by the pinned schema.
Signature
Section titled “Signature”auth.finishPasskeyLogin#9857ad07 flags:# credential:InputPasskeyCredential from_dc_id:flags.0?int from_auth_key_id:flags.0?long = auth.Authorization;Result type
Section titled “Result type”auth.Authorization
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| credential | InputPasskeyCredential | — | — | No description provided by the pinned schema. |
| from_dc_id | flags.0?int | flags.0 | — | No description provided by the pinned schema. |
| from_auth_key_id | flags.0?long | flags.0 | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| from_dc_id | 0 | Controlled by flags; present when this bit is set. |
| from_auth_key_id | 0 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import AuthFinishPasskeyLoginPublic access: miniproto.raw.functions.AuthFinishPasskeyLogin.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import AuthFinishPasskeyLogin
# Naming the raw request class is local only; it performs no I/O or network request.request_type = AuthFinishPasskeyLoginResult 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 | CREDENTIAL_INVALID | The specified credential is invalid. |
| 400 | PASSKEY_ORIGIN_MISMATCH | Third-party clients currently don’t support passkeys even when changing the origin. |
| 500 | AUTH_RESTART | Restart the authorization process. |
Accepted types
Section titled “Accepted types”InputPasskeyCredential
Known selected constructors: inputPasskeyCredentialFirebasePNV, inputPasskeyCredentialPublicKey
Returned types
Section titled “Returned types”auth.Authorization
Known selected constructors: auth.authorization, auth.authorizationSignUpRequired
Related methods
Section titled “Related methods”account.registerPasskey, auth.checkPassword, auth.finishFirebasePnvLogin, auth.firebasePnvSignUp, auth.importAuthorization, auth.importBotAuthorization, auth.importWebTokenAuthorization, auth.recoverPassword, auth.signIn, auth.signUp
Availability evidence
Section titled “Availability evidence”- unauthenticated allowed
- user only
Provenance
Section titled “Provenance”- 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 229 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=78; core_only_count=18; overlap_count=2285; tdlib_only_count=195
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2470; tdesktop_only=null; tdlib_only=accessPointRule, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret