Update Sent Message imbot.message.update
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: an authorized user of the application that registered the chat bot. The method only works with bots from this application.
DEPRECATED
Development of this method has been halted. Please use imbot.v2.Chat.Message.update.
The method imbot.message.update modifies a previously sent message from the chat bot.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
BOT_ID |
The identifier of the chat bot. It can be obtained using the imbot.bot.list method. If the parameter is not provided, the method searches for the first bot registered by the current application. |
|
MESSAGE_ID* |
The identifier of the message to be modified. The value must be greater than For messages sent by the bot via REST, the identifier is returned by the imbot.message.add method. |
|
MESSAGE |
The new text of the message. If an empty value is provided, the message will be deleted. If the parameter is not provided, the message text will remain unchanged. |
|
An attachment with content blocks: images, links, files. You can provide:
For more details, refer to the Attachments section. An empty value or |
|
|
Buttons under the message that the user can interact with. For more information, see the article Working with Keyboards. An empty value or |
|
|
Additional items in the chat's context menu. For more details, refer to the article Context Menu. An empty value or |
|
|
URL_PREVIEW |
Controls the display of links: when enabled, the link is shown as a "rich link" with a card. Allowed values:
|
|
SKIP_CONNECTOR |
Skips sending the message to external connectors of open channels when updating Allowed values:
|
|
CLIENT_ID |
This parameter is required only for webhooks. Pass the same CLIENT_ID that was specified when registering the chat bot. |
Code Examples
How to Use Examples in Documentation
curl -X POST /
-H "Content-Type: application/json" /
-H "Accept: application/json" /
-d '{"BOT_ID":39,"MESSAGE_ID":19880117,"MESSAGE":"Updated text","URL_PREVIEW":"Y","CLIENT_ID":"**put_your_client_id_here**"}' /
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.message.update
curl -X POST /
-H "Content-Type: application/json" /
-H "Accept: application/json" /
-d '{"BOT_ID":39,"MESSAGE_ID":19880117,"MESSAGE":"Updated text","URL_PREVIEW":"Y","auth":"**put_access_token_here**"}' /
https://**put_your_bitrix24_address**/rest/imbot.message.update
try {
const response = await $b24.callMethod('imbot.message.update', {
BOT_ID: 39,
MESSAGE_ID: 19880117,
MESSAGE: 'Updated text',
URL_PREVIEW: 'Y',
});
const { result } = response.getData();
console.log('Updated:', result);
} catch (error) {
console.error('Error updating message:', error);
}
try {
$response = $b24Service
->core
->call(
'imbot.message.update',
[
'BOT_ID' => 39,
'MESSAGE_ID' => 19880117,
'MESSAGE' => 'Updated text',
'URL_PREVIEW' => 'Y',
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
echo 'Updated: ' . ($result->data() ? 'true' : 'false');
}
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error updating message: ' . $exception->getMessage();
}
BX24.callMethod(
'imbot.message.update',
{
BOT_ID: 39,
MESSAGE_ID: 19880117,
MESSAGE: 'Updated text',
URL_PREVIEW: 'Y',
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imbot.message.update',
[
'BOT_ID' => 39,
'MESSAGE_ID' => 19880117,
'MESSAGE' => 'Updated text',
'URL_PREVIEW' => 'Y',
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Updated: ' . ($result['result'] ? 'true' : 'false');
}
Response Handling
HTTP Code: 200
{
"result": true,
"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",
"operating_reset_at": 1762349466,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
|
|
time |
Information about the request execution time. |
Error Handling
HTTP Status: 400, 403
{
"error": "MESSAGE_ID_ERROR",
"error_description": "Message ID can't be empty"
}
|
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 not found |
The bot is not found or the application does not have an available bot for auto-filling |
|
|
Bot was installed by another REST application |
The provided |
|
|
Message ID can't be empty |
A valid |
|
|
Incorrect attach params |
Invalid structure of |
|
|
You have exceeded the maximum allowable size of attach |
The allowable size of |
|
|
Incorrect keyboard params |
Invalid structure of |
|
|
You have exceeded the maximum allowable size of keyboard |
The allowable size of |
|
|
Incorrect menu params |
Invalid structure of |
|
|
You have exceeded the maximum allowable size of menu |
The allowable size of |
|
|
Time has expired for modification or you don't have access |
No access to modify the message or the editing time has expired — more than three days have passed since publication. |
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
- Send Message imbot.message.add
- Delete Message imbot.message.delete
- Set "Like" for the message imbot.message.like
- Event on Message Update ONIMBOTMESSAGEUPDATE