Add Reaction to Message imbot.v2.Chat.Message.Reaction.add

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.Reaction.add adds a bot reaction to a message.

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`	Message ID
reaction* `string`	Reaction code. The list of available codes is described below

Available Reaction Codes

Code	Description
`like`	Like
`dislike`	Dislike
`faceWithTearsOfJoy`	Laughing to tears
`redHeart`	Heart
`neutralFace`	Indifferent
`fire`	Fire!
`cry`	Sad
`slightlySmilingFace`	Smiling
`winkingFace`	Winking
`laugh`	Laughing
`kiss`	Admiring
`wonder`	Shocked
`slightlyFrowningFace`	Frowning
`loudlyCryingFace`	Crying loudly
`faceWithStuckOutTongue`	Tongue out
`faceWithStuckOutTongueAndWinkingEye`	Teasing
`smilingFaceWithSunglasses`	Cool
`confusedFace`	Not sure
`flushedFace`	Embarrassed
`thinkingFace`	Doubting
`angry`	Angry
`smilingFaceWithHorns`	Smirking
`faceWithThermometer`	Sick
`facepalm`	No comment
`poo`	Yuck
`flexedBiceps`	Strong
`clappingHands`	Awesome
`raisedHand`	High five
`smilingFaceWithHeartEyes`	Beautiful
`smilingFaceWithHearts`	Love it
`pleadingFace`	Please
`relievedFace`	Zen
`foldedHands`	Thank you
`okHand`	OK
`signHorns`	Rock!
`loveYouGesture`	All good
`clownFace`	Clown
`partyingFace`	Congratulations
`questionMark`	Question
`exclamationMark`	Attention
`lightBulb`	Idea
`bomb`	Bomb
`sleepingSymbol`	Sleeping
`crossMark`	Cancel
`whiteHeavyCheckMark`	Done
`eyes`	Eyes
`handshake`	Deal
`hundredPoints`	Support

The list of reactions may expand or contract without prior notice.

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"botId":456,"botToken":"my_bot_token","messageId":789,"reaction":"like"}' \
          https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.v2.Chat.Message.Reaction.add

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"botId":456,"messageId":789,"reaction":"like","auth":"**put_access_token_here**"}' \
          https://**put_your_bitrix24_address**/rest/imbot.v2.Chat.Message.Reaction.add

try {
          const response = await $b24.callMethod('imbot.v2.Chat.Message.Reaction.add', {
            botId: 456,
            messageId: 789,
            reaction: 'like',
          });
        
          const { result } = response.getData();
          console.log('result:', result);
        } catch (error) {
          console.error('Error:', error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'imbot.v2.Chat.Message.Reaction.add',
                    [
                        'botId' => 456,
                        'messageId' => 789,
                        'reaction' => 'like',
                    ]
                );
        
            $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.Reaction.add',
            {
                botId: 456,
                messageId: 789,
                reaction: 'like',
            },
            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.Reaction.add',
            [
                'botId' => 456,
                'messageId' => 789,
                'reaction' => 'like',
            ]
        );
        
        if (!empty($result['error'])) {
            echo 'Error: ' . $result['error_description'];
        } else {
            echo 'Reaction added';
        }

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 reaction was successfully added
time `time`	Information about the request execution time

Error Handling

HTTP Status: 400, 403

{
            "error": "REACTION_NOT_FOUND",
            "error_description": "Reaction not found"
        }

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 provided. Required for webhook authorization
`BOT_ID_REQUIRED`	Bot ID is required	`botId` is not provided
`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	Bot is not a participant in the chat with this message
`REACTION_NOT_FOUND`	Reaction not found	Non-existent reaction code specified
`REACTION_ALREADY_SET`	Reaction already set	This reaction is already set by the bot on this message

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

Get Message Context

Remove Reaction from Message

Add Reaction to Message imbot.v2.Chat.Message.Reaction.add

Method ParametersMethod Parameters

Available Reaction CodesAvailable Reaction Codes

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning