auth.resetLoginEmail

auth.resetLoginEmail

No description provided by the pinned schema.

Signature

auth.resetLoginEmail#7e960193 phone_number:string phone_code_hash:string = auth.SentCode;

Result type

auth.SentCode

Parameters

Name	Type	Flag	Default	Description
phone_number	string	—	—	No description provided by the pinned schema.
phone_code_hash	string	—	—	No description provided by the pinned schema.

Python binding

from miniproto.raw.functions import AuthResetLoginEmail

Public access: miniproto.raw.functions.AuthResetLoginEmail.

Safe usage shape

from miniproto.raw.functions import AuthResetLoginEmail

# Naming the raw request class is local only; it performs no I/O or network request.
request_type = AuthResetLoginEmail

Result family

auth.SentCode

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	EMAIL_INSTALL_MISSING	Attempting to send a code to the recovery email, but no email is configured.
400	PHONE_NUMBER_INVALID	The phone number is invalid.
400	TASK_ALREADY_EXISTS	An email reset was already requested.

Accepted types

No non-primitive type relationships were found.

Returned types

auth.SentCode Known selected constructors: auth.sentCode, auth.sentCodePaymentRequired, auth.sentCodeSuccess

Related methods

account.sendChangePhoneCode, account.sendConfirmPhoneCode, account.sendVerifyPhoneCode, auth.checkPaidAuth, auth.resendCode, auth.sendCode

Availability evidence

• unauthenticated allowed
• user only

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

• 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