Telegram Passkey and login email
Manage sign-in options for your Telegram accounts in Deskgram 2. The account panel supports Passkey registration and linking a login email with a verification code. Check the result for each account.
Telegram Passkey and login email
Manage sign-in options for your Telegram accounts in Deskgram 2. The account panel supports Passkey registration and linking a login email with a verification code. Check the result for each account.
Download Deskgram 2 PlansModule settings
Select accounts in the account panel, choose Register Passkey and confirm the task. Registration uses an authorized session and checks Telegram settings_display_passkeys, existing server keys and the key limit. Existing keys are not registered again by default. Availability depends on the account, session, API client and Telegram response. Deskgram stores the credential in account JSON with an encrypted private key. The aesgcm-hwid-license-v1 scheme uses HWID and the license key; copying JSON to another computer or changing the license does not establish that decryption will work. A server-side Passkey without a usable local credential is not sufficient for Deskgram recovery. The Telethon → Telethon converter has a separate Passkey login method for creating a new session from an already saved key. An enabled 2FA password may still be required. For login email, select exactly one account, open Bind login email, enter your address, request a code and confirm it from the email. Initial setup may use a separate login-email flow when the API allows it.
Check before running
Passkey registration, local key availability and a successful new login are separate results. Inspect each account result and preserve its JSON with the account backup. Do not assume that task completion means every selected account succeeded. Sending an email code only creates a pending verification; successful confirmation saves login_email and login_email_verified. Check the address and confirmed status. An invalid or expired code does not confirm the binding; request another code when needed. Telegram can reject an address or require a different initial setup flow. Login email receives sign-in codes, while 2FA recovery email concerns the cloud password. Linking login email does not change that password or verify its recovery address. Check EMAIL_INVALID, EMAIL_NOT_ALLOWED and Telegram restrictions in the log. The feature does not promise recovery of deleted accounts or removal of restrictions.
Related tasks and guides
Choose a related task or open the detailed guide. Linked Russian guides are marked accordingly.
Telegram API Support Compare software