upload.getFile
Returns content of a whole file or its part.
Example
TL schema
Parameters
Name | Type | Description |
flags | Flags, see TL conditional fields | |
precise | Disable some checks on limit and offset values, useful for example to stream videos by keyframes | |
cdn_supported | Whether the current client supports CDN downloads | |
location | File location | |
offset | Number of bytes to be skipped | |
limit | Number of bytes to be returned |
Result
Possible errors
Code | Type | Description |
401 | AUTH_KEY_PERM_EMPTY | The temporary auth key must be binded to the permanent auth key to use these methods. |
400 | CHANNEL_INVALID | The provided channel is invalid |
400 | CHANNEL_PRIVATE | You haven't joined this channel/supergroup |
406 | FILEREF_UPGRADE_NEEDED | The client has to be updated in order to support file references |
400 | FILE_ID_INVALID | The provided file id is invalid |
400 | FILE_REFERENCE_* | The file reference expired, it must be refreshed |
400 | FILE_REFERENCE_EXPIRED | File reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference |
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 |
Can bots use this methd ?
yes
Related pages
How to handle file references.
How to handle file references.
Last updated