messages.uploadEncryptedFile
messages.uploadEncryptedFile
Section titled “messages.uploadEncryptedFile”No description provided by the pinned schema.
Signature
Section titled “Signature”messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;Result type
Section titled “Result type”EncryptedFile
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| peer | InputEncryptedChat | — | — | No description provided by the pinned schema. |
| file | InputEncryptedFile | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import MessagesUploadEncryptedFilePublic access: miniproto.raw.functions.MessagesUploadEncryptedFile.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import MessagesUploadEncryptedFile
# Naming the raw request class is local only; it performs no I/O or network request.request_type = MessagesUploadEncryptedFileResult 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 | CHAT_ID_INVALID | The provided chat id is invalid. |
| 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”InputEncryptedChat, InputEncryptedFile
Known selected constructors: inputEncryptedChat, inputEncryptedFile, inputEncryptedFileBigUploaded, inputEncryptedFileEmpty, inputEncryptedFileUploaded
Returned types
Section titled “Returned types”EncryptedFile
Known selected constructors: encryptedFile, encryptedFileEmpty
Related methods
Section titled “Related methods”messages.acceptEncryption, messages.readEncryptedHistory, messages.reportEncryptedSpam, messages.sendEncrypted, messages.sendEncryptedFile, messages.sendEncryptedService, messages.setEncryptedTyping
Availability evidence
Section titled “Availability evidence”- 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