account.updateUsername
account.updateUsername
Section titled “account.updateUsername”No description provided by the pinned schema.
Signature
Section titled “Signature”account.updateUsername#3e0bdd7c username:string = User;Result type
Section titled “Result type”User
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| username | string | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import AccountUpdateUsernamePublic access: miniproto.raw.functions.AccountUpdateUsername.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import AccountUpdateUsername
# Naming the raw request class is local only; it performs no I/O or network request.request_type = AccountUpdateUsernameResult family
Section titled “Result family”RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | USERNAME_INVALID | The provided username is not valid. |
| 400 | USERNAME_NOT_MODIFIED | The username was not modified. |
| 400 | USERNAME_OCCUPIED | The provided username is already occupied. |
| 400 | USERNAME_PURCHASE_AVAILABLE | The specified username can be purchased on https://fragment.com. |
| 401 | AUTH_KEY_UNREGISTERED | The specified authorization key is not registered in the system (for example, a PFS temporary key has expired). |
Accepted types
Section titled “Accepted types”No non-primitive type relationships were found.
Returned types
Section titled “Returned types”User
Known selected constructors: user, userEmpty
Related methods
Section titled “Related methods”account.changePhone, account.updateProfile, bots.createBot, bots.getAdminedBots, channels.getMessageAuthor, contacts.importContactToken, messages.getFutureChatCreatorAfterLeave, users.getUsers
Availability evidence
Section titled “Availability evidence”- 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