Upload File to Chat imbot.v2.File.upload
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
imbotWho can execute the method: owner of the registered bot
The method imbot.v2.File.upload uploads a file to the chat on behalf of the bot. It combines three steps of the deprecated API into a single call: uploading the file to the Drive, attaching it to the chat, and sending a message.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
botId* |
Bot ID |
|
botToken |
Unique authorization token for the bot. Required for webhook authorization, not needed for OAuth. Pass the same botToken that was specified during the registration of the chat bot |
|
dialogId* |
Dialog ID. For group chats — |
|
fields* |
File and message data. The structure is described below |
Parameter fields
|
Name |
Description |
|
name* |
File name with extension |
|
content* |
File content in Base64 encoding. Maximum size — 100 MB |
|
message |
Text message sent along with the file |
How to prepare the value for content:
- Read the file in binary mode.
- Encode the content in Base64.
- Pass only the Base64 string, without the prefix
data:*/*;base64,.
More details: How to upload files.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"botId":456,"botToken":"my_bot_token","dialogId":"chat5","fields":{"name":"report.pdf","content":"SGVsbG8gV29ybGQh","message":"Here is the report"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.v2.File.upload
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"botId":456,"dialogId":"chat5","fields":{"name":"report.pdf","content":"SGVsbG8gV29ybGQh","message":"Here is the report"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/imbot.v2.File.upload
try {
const response = await $b24.callMethod('imbot.v2.File.upload', {
botId: 456,
dialogId: 'chat5',
fields: { name: 'report.pdf', content: 'SGVsbG8gV29ybGQh', message: 'Here is the report' },
});
const { result } = response.getData();
console.log('result:', result);
} catch (error) {
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'imbot.v2.File.upload',
[
'botId' => 456,
'dialogId' => 'chat5',
'fields' => [
'name' => 'report.pdf',
'content' => base64_encode(file_get_contents('/path/to/report.pdf')),
'message' => 'Here is the report',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'result: '. print_r($result, true);
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error: '. $exception->getMessage();
}
BX24.callMethod(
'imbot.v2.File.upload',
{
botId: 456,
dialogId: 'chat5',
fields: { name: 'report.pdf', content: btoa('...'), message: 'Here is the report' },
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imbot.v2.File.upload',
[
'botId' => 456,
'dialogId' => 'chat5',
'fields' => [
'name' => 'report.pdf',
'content' => base64_encode(file_get_contents('/path/to/report.pdf')),
'message' => 'Here is the report',
],
]
);
if (!empty($result['error'])) {
echo 'Error: '. $result['error_description'];
} else {
echo 'File ID: '. $result['result']['file']['id'];
}
Response Handling
HTTP Code: 200
{
"result": {
"file": {
"id": 138,
"chatId": 5,
"name": "report.pdf",
"extension": "pdf",
"size": 35341
},
"messageId": 123,
"chatId": 5,
"dialogId": "chat5"
},
"time": {
"start": 1728626400.123,
"finish": 1728626400.234,
"duration": 0.111,
"processing": 0.045,
"date_start": "2024-10-11T10:00:00+02:00",
"date_finish": "2024-10-11T10:00:00+02:00"
}
}
Returned Data
|
Name |
Description |
|
result |
Result of the operation |
|
result.file |
Data of the uploaded file (detailed description) |
|
result.messageId |
ID of the created message with the file |
|
result.chatId |
Numeric ID of the chat |
|
result.dialogId |
Dialog ID |
|
time |
Information about the request execution time |
Fields of the File Object
|
Field |
Description |
|
id |
File identifier |
|
chatId |
Chat identifier |
|
name |
File name |
|
extension |
File extension |
|
size |
File size in bytes |
Complete description of all object fields can be found on the Objects and Fields page.
Error Handling
HTTP Status: 400, 403
{
"error": "FILE_TOO_LARGE",
"error_description": "File too large"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Description |
Value |
|
|
Bot token is not specified |
|
|
|
Bot ID is required |
|
|
|
Bot not found |
Bot not found |
|
|
Bot is registered by another application |
Bot is registered by another application |
|
|
File name or content is empty |
File name or content is not specified |
|
|
Invalid base64 content |
Invalid Base64 |
|
|
Failed to get chat folder |
Failed to get chat folder |
|
|
File upload failed |
File upload error |
|
|
Failed to send message |
Message sending error |
|
|
File is too large |
File size exceeds 100 MB |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- API imbot.v2 Change Log
- Get Download Link for imbot.v2.File.download
- Send Message imbot.v2.Chat.Message.send