upload.getFile
upload.getFile
Section titled “upload.getFile”No description provided by the pinned schema.
Signature
Section titled “Signature”upload.getFile#be5335be flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:long limit:int = upload.File;Result type
Section titled “Result type”upload.File
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| precise | flags.0?true | flags.0 | — | No description provided by the pinned schema. |
| cdn_supported | flags.1?true | flags.1 | — | No description provided by the pinned schema. |
| location | InputFileLocation | — | — | No description provided by the pinned schema. |
| offset | long | — | — | No description provided by the pinned schema. |
| limit | int | — | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| precise | 0 | Controlled by flags; present when this bit is set. |
| cdn_supported | 1 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import UploadGetFilePublic access: miniproto.raw.functions.UploadGetFile.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import UploadGetFile
# Naming the raw request class is local only; it performs no I/O or network request.request_type = UploadGetFileResult 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 | CDN_METHOD_INVALID | You can’t call this method in a CDN DC. |
| 400 | CHANNEL_INVALID | The provided channel is invalid. |
| 400 | CHANNEL_PRIVATE | You haven’t joined this channel/supergroup. |
| 400 | FILE_ID_INVALID | The provided file id is invalid. |
| 400 | FILE_REFERENCE_EMPTY | An empty file reference was specified. |
| 400 | FILE_REFERENCE_EXPIRED | File reference expired, it must be refetched as described in the documentation. |
| 400 | FILE_REFERENCE_INVALID | The specified file reference is invalid. |
| 400 | LIMIT_INVALID | The provided limit is invalid. |
| 400 | LOCATION_INVALID | The provided location is invalid. |
| 400 | MSG_ID_INVALID | Invalid message ID provided. |
| 400 | OFFSET_INVALID | The provided offset is invalid. |
| 400 | PEER_ID_INVALID | The provided peer 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). |
| 406 | FILEREF_UPGRADE_NEEDED | The client has to be updated in order to support file references. |
| 420 | FLOOD_PREMIUM_WAIT_%d | Please wait %d seconds before repeating the action, or purchase a Telegram Premium subscription to remove this rate limit. |
Accepted types
Section titled “Accepted types”InputFileLocation
Known selected constructors: inputDocumentFileLocation, inputEncryptedFileLocation, inputFileLocation, inputGroupCallStream, inputPeerPhotoFileLocation, inputPeerPhotoFileLocationLegacy, inputPhotoFileLocation, inputPhotoLegacyFileLocation, inputSecureFileLocation, inputStickerSetThumb, inputStickerSetThumbLegacy, inputTakeoutFileLocation
Returned types
Section titled “Returned types”upload.File
Known selected constructors: upload.file, upload.fileCdnRedirect
Related methods
Section titled “Related methods”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
miniprotoFast paths where they count. Explicit boundaries everywhere else.