Update Message im.message.update

Choose a tool for developing with an AI agent:

  • use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
  • use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

Scope: im

Who can execute the method: message author

The method im.message.update modifies the text and parameters of an already sent message.

Method Parameters

Required parameters are marked with *

Name
type

Description

MESSAGE_ID*
integer

Identifier of the message.

The identifier is returned by the method im.message.add

MESSAGE
string

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

ATTACH
object
string

Attachment with content blocks: images, links, files. To remove the attachment, pass N or an empty value.

Read more in the Attachments section

KEYBOARD
object
string

Buttons below the message that the user can interact with. To disable button display, pass N or an empty value.

Read more in the Working with Keyboards article

MENU
object
string

Additional items in the chat's context menu. To disable the display of additional menu items, pass N or an empty value.

Read more in the Context Menu article

URL_PREVIEW
string

Conversion of links into rich links.

Allowed values:

  • Y — enabled
  • N — disabled

IS_EDITED
string

Flag for marking "edited":

  • Y — mark
  • N — do not mark

Default is Y

The parameter is applied when updating ATTACH. When changing MESSAGE, the "edited" label may appear even if IS_EDITED = 'N' is provided.

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"MESSAGE_ID":34239,"MESSAGE":"Updated text","KEYBOARD":"N"}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/im.message.update
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"MESSAGE_ID":34239,"MESSAGE":"Updated text","KEYBOARD":"N","auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/im.message.update
        
// This snippet is an ES module: top-level await requires type="module" or a bundler.
        // $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
        import { Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        try {
          const response = await $b24.actions.v2.call.make<boolean>({
            method: 'im.message.update',
            params: {
              MESSAGE_ID: 34239,
              MESSAGE: 'Updated text',
              KEYBOARD: 'N',
            },
            requestId: Text.getUuidRfc4122()
          })
        
          // The payload is available only on a successful response
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('Message updated:', result)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }
        
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
        <script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function updateMessage() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'im.message.update',
                params: {
                  MESSAGE_ID: 34239,
                  MESSAGE: 'Updated text',
                  KEYBOARD: 'N',
                },
                requestId: B24Js.Text.getUuidRfc4122()
              })
        
              // The payload is available only on a successful response
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('Message updated:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', updateMessage)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.im.message.update(
                message_id=34239,
                message="Updated text",
                keyboard="N",
            ).response
            result = bitrix_response.result
            print(result)
        except BitrixAPIError as error:
            print(
                "Bitrix API error",
                f"error: {error.error}",
                f"error_description: {error.error_description}",
                sep="\n",
            )
        except BitrixSDKException as error:
            print(f"Bitrix SDK error: {error.message}")
        except Exception as error:
            print(f"Unexpected error: {error}")
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'im.message.update',
                    [
                        'MESSAGE_ID' => 34239,
                        'MESSAGE' => 'Updated text',
                        'KEYBOARD' => 'N'
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error updating message: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'im.message.update',
            {
                MESSAGE_ID: 34239,
                MESSAGE: 'Updated text',
                KEYBOARD: 'N'
            },
            function(result)
            {
                if (result.error())
                    console.error(result.error());
                else
                    console.log(result.data());
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'im.message.update',
            [
                'MESSAGE_ID' => 34239,
                'MESSAGE' => 'Updated text',
                'KEYBOARD' => 'N'
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "im.message.update", b24.Params{
        	"MESSAGE_ID": 34239,
        	"MESSAGE":    "Updated text",
        	"KEYBOARD":   "N",
        })
        if err != nil {
        	return fmt.Errorf("im.message.update: %w", err)
        }
        
        var ok bool
        if err := json.Unmarshal(res.Result, &ok); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        fmt.Println("done:", ok)
        

Response Handling

HTTP Status: 200

{
            "result": true,
            "time": {
                "start": 1772623160,
                "finish": 1772623160.616113,
                "duration": 0.6161129474639893,
                "processing": 0,
                "date_start": "2026-03-04T14:19:20+01:00",
                "date_finish": "2026-03-04T14:19:20+01:00",
                "operating_reset_at": 1772623760,
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
boolean

true if the message was updated

time
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
type

Description

error
string

String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only error_description shows the reason

error_description
string

Error message for the developer. Do not show it to the end user without processing

Possible Error Codes

Code

Description

Value

MESSAGE_ID_ERROR

Message ID can't be empty

MESSAGE_ID is missing or invalid

CANT_EDIT_MESSAGE

Time has expired for modification or you don't have access

No permission to edit the message or the modification period has expired

ATTACH_ERROR

Incorrect attach params

Invalid ATTACH object

ATTACH_OVERSIZE

You have exceeded the maximum allowable size of attach

The size of ATTACH exceeds the allowable limit

KEYBOARD_ERROR

Incorrect keyboard params

Invalid KEYBOARD object

KEYBOARD_OVERSIZE

You have exceeded the maximum allowable size of keyboard

The size of KEYBOARD exceeds the allowable limit

menu_ERROR

Incorrect menu params

Invalid MENU object

MENU_OVERSIZE

You have exceeded the maximum allowable size of menu

The size of MENU exceeds the allowable limit

Statuses and System Error Codes

HTTP Status: 4xx, 5xx

The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

429

OPERATION_TIME_LIMIT
Method is blocked due to operation time limit

The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit

401

NO_AUTH_FOUND
Wrong authorization data

The request contains no authorization data: neither an access token nor a webhook code was passed

401

INVALID_REQUEST
Https required

Methods are called over the HTTPS protocol only

401

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support

401

ACCESS_DENIED
REST is available only on commercial plans

REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — REST is available only by subscription

401

INVALID_CREDENTIALS
Invalid request credentials

No active webhook with the specified user identifier and secret code was found

404

ERROR_METHOD_NOT_FOUND
Method not found!

No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope

401

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

The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with provided by the access token

401

expired_token
The access token provided has expired

The access token has expired

401

user_access_error
The user does not have access to the application

The application is installed, but the Bitrix24 administrator has granted access to it only to specific users

403

PORTAL_DELETED
Portal was deleted

The public part of the site is closed. To open it 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