Interacting with Notification Buttons im.notify.confirm

Scope: im

Who can execute the method: any user

The method im.notify.confirm sends the selected value of the notification button.

Method Parameters

Required parameters are marked with *

Name
Type

Description

NOTIFY_ID*
integer

Identifier of the notification with buttons.

You can obtain the notification identifier using the im.notify.get method.

NOTIFY_VALUE*
string

Value of the selected button.

For example, consider a notification that supports buttons:

  • Accept — value 'Y'
  • Decline — value 'N'

Example of buttons

Code Examples

How to Use Examples in Documentation

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"NOTIFY_ID":288,"NOTIFY_VALUE":"Y"}' \
          https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/im.notify.confirm
        
curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"NOTIFY_ID":288,"NOTIFY_VALUE":"Y","auth":"**put_access_token_here**"}' \
          https://**put_your_bitrix24_address**/rest/im.notify.confirm
        
try {
          const response = await $b24.callMethod('im.notify.confirm', {
            NOTIFY_ID: 288,
            NOTIFY_VALUE: 'Y',
          });
        
          const { result } = response.getData();
          console.log(result);
        } catch (error) {
          console.error(error);
        }
        
try {
            $response = $b24Service->core->call(
                'im.notify.confirm',
                [
                    'NOTIFY_ID' => 288,
                    'NOTIFY_VALUE' => 'Y',
                ]
            );
        
            $result = $response->getResponseData()->getResult();
        
            if ($result->error()) {
                echo 'Error: ' . $result->error();
            } else {
                var_dump($result->data());
            }
        } catch (Throwable $exception) {
            echo $exception->getMessage();
        }
        
BX24.callMethod(
            'im.notify.confirm',
            {
                NOTIFY_ID: 288,
                NOTIFY_VALUE: 'Y',
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error().ex);
                } else {
                    console.log(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'im.notify.confirm',
            [
                'NOTIFY_ID' => 288,
                'NOTIFY_VALUE' => 'Y',
            ]
        );
        
        if (!empty($result['error'])) {
            echo 'Error: ' . $result['error_description'];
        } else {
            var_dump($result['result']);
        }
        

Response Handling

HTTP Code: 200

{
            "result": {
                "result_message": [
                    "Invitation accepted"
                ]
            },
            "time": {
                "start": 1760000000.0,
                "finish": 1760000000.1,
                "duration": 0.1,
                "processing": 0.04,
                "date_start": "2026-03-02T09:30:00+01:00",
                "date_finish": "2026-03-02T09:30:00+01:00",
                "operating_reset_at": 1760030000,
                "operating": 0
            }
        }
        

Returned Data

Name
Type

Description

result
object

Object containing the result of the button press.

The structure of the object is described in detail below

time
time

Information about the request execution time

Result Object

Name
Type

Description

result_message
array
boolean

Response from the notification button handler. May contain an array of strings or false

Error Handling

HTTP Status: 400

{
            "error": "NOTIFY_VALUE_ERROR",
            "error_description": "Notification Value can't be empty"
        }
        

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

ID_ERROR

Notification ID can't be empty

Parameter NOTIFY_ID is not provided or <= 0

NOTIFY_VALUE_ERROR

Notification Value can't be empty

Empty parameter NOTIFY_VALUE

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 allowed to be called 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 methods must be called using the HTTPS protocol

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is available only on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users

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 option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning