Update Message imbot.v2.Chat.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: imbot

Who can execute the method: owner of the registered bot

The method imbot.v2.Chat.Message.update updates a bot's message. A bot can only update its own messages.

Messages sent with the parameter system: true cannot be updated—they have authorId = 0 and do not belong to the bot in terms of access permissions.

Method Parameters

Required parameters are marked with *

Name
Type

Description

botId*
integer

Bot ID

botToken
string

Unique authorization token for the bot. Required for webhook authorization, not needed for OAuth.

Pass the same botToken that was specified during the chat bot registration

messageId*
integer

ID of the message to be updated

fields*
object

Fields of the message to be updated. The structure of the object is described below

Parameter fields

Name
Type

Description

message
string

New text of the message. Maximum length—20,000 characters

attach
array

New attachments. More details: How to use attachments

keyboard
array

New keyboard. More details: Working with keyboards. To remove the keyboard, pass "N"

urlPreview
string

Show link previews. Acceptable values: Y, N. Default is Y

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","messageId":789,"fields":{"message":"Updated text"}}' \
          https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.v2.Chat.Message.update
        
curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"botId":456,"messageId":789,"fields":{"message":"Updated text"},"auth":"**put_access_token_here**"}' \
          https://**put_your_bitrix24_address**/rest/imbot.v2.Chat.Message.update
        
try {
          const response = await $b24.callMethod('imbot.v2.Chat.Message.update', {
            botId: 456,
            messageId: 789,
            fields: { message: 'Updated text' },
          });
        
          const { result } = response.getData();
          console.log('result:', result);
        } catch (error) {
          console.error('Error:', error);
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'imbot.v2.Chat.Message.update',
                    [
                        'botId' => 456,
                        'messageId' => 789,
                        'fields' => ['message' => 'Updated text'],
                    ]
                );
        
            $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.Chat.Message.update',
            {
                botId: 456,
                messageId: 789,
                fields: { message: 'Updated text' },
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error().ex);
                } else {
                    console.log(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'imbot.v2.Chat.Message.update',
            [
                'botId' => 456,
                'messageId' => 789,
                'fields' => ['message' => 'Updated text'],
            ]
        );
        
        if (!empty($result['error'])) {
            echo 'Error: ' . $result['error_description'];
        } else {
            echo 'Updated';
        }
        

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"
            }
        }
        

Returned Data

Name
Type

Description

result
boolean

true if the update was successful

time
time

Information about the execution time of the request

Error Handling

HTTP Status: 400, 403

{
            "error": "ACCESS_DENIED",
            "error_description": "Access denied"
        }
        

Name
type

Description

error
string

String error code. It may consist of digits, Latin letters, and underscores

error_description
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_NOT_SPECIFIED

Bot token is not specified

botToken is not specified. Required for webhook authorization

BOT_ID_REQUIRED

Bot ID is required

botId is not specified

BOT_NOT_FOUND

Bot not found

Bot not found

BOT_OWNERSHIP_ERROR

Bot is registered by another application

Bot is registered by another application

ACCESS_DENIED

Access denied

The message does not belong to the bot or does not exist. The bot can only update its own messages

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

405

ERROR_BATCH_METHOD_NOT_ALLOWED
Method is not allowed for batch usage

The current method is not permitted for calls using batch

400

ERROR_BATCH_LENGTH_EXCEEDED
Max batch length exceeded

The maximum length of parameters passed to the batch method has been exceeded

401

NO_AUTH_FOUND
Wrong authorization data

Invalid access token or webhook code

400

INVALID_REQUEST
Https required

The HTTPS protocol is required for method calls

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is only available on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user associated with the access token or webhook used to call the method lacks the necessary permissions

404

ERROR_MANIFEST_IS_NOT_AVAILABLE
Manifest is not available

The manifest is not available

403

insufficient_scope
The request requires higher privileges than provided by the webhook token

The request requires higher privileges than those provided by the webhook token

401

expired_token
The access token provided has expired

The provided access token has expired

403

user_access_error
The user does not have access to the application

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

500

PORTAL_DELETED
Portal was deleted

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