Searching Notification History im.notify.history.search

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: im

Who can execute the method: any user

The method im.notify.history.search performs a search through the user's notification history.

Notifications are sorted first by descending creation date, then by descending identifiers.

Method Parameters

Required parameters are marked with *

Name `Type`	Description
SEARCH_TEXT `string`	Search text. If `SEARCH_TYPE` and `SEARCH_DATE` are not specified, the string length must be at least `3` characters
SEARCH_TYPE `string`	Filter by notification type in the format `MODULE` or `MODULE\|EVENT`. Ready values can be obtained using the method im.notify.schema.get
SEARCH_TYPES `array`	Array of filters by notification types in the format `MODULE` or `MODULE\|EVENT`
SEARCH_DATE `string`	Date filter in ISO 8601 format (RFC3339)
SEARCH_DATE_FROM `string`	Start of the date range in ISO 8601 format (RFC3339). Used together with `SEARCH_DATE_TO`
SEARCH_DATE_TO `string`	End of the date range in ISO 8601 format (RFC3339). Used together with `SEARCH_DATE_FROM`
SEARCH_AUTHORS `array`	Array of notification author identifiers for filtering
LAST_ID `integer`	Identifier of the last notification from the previous page to load the next one. Usually taken from the `id` field of the last element in the `notifications` array in the response of the previous search step or in the response of im.notify.get
LIMIT `integer`	Number of notifications per page. Default value is `50`. Maximum value is `50`
CONVERT_TEXT `string`	Convert notification text. Value `Y` enables conversion, any other value disables it
GROUP_TAG `string`	Group tag for notifications for additional filtering

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 '{"SEARCH_TEXT":"invoice","SEARCH_TYPE":"tasks|task_update","SEARCH_DATE":"2026-03-03T16:52:29+01:00","LAST_ID":1500,"LIMIT":20,"CONVERT_TEXT":"Y","GROUP_TAG":"TASK|42"}' \
          https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/im.notify.history.search

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"SEARCH_TEXT":"invoice","SEARCH_TYPE":"tasks|task_update","SEARCH_DATE":"2026-03-03T16:52:29+01:00","LAST_ID":1500,"LIMIT":20,"CONVERT_TEXT":"Y","GROUP_TAG":"TASK|42","auth":"**put_access_token_here**"}' \
          https://**put_your_bitrix24_address**/rest/im.notify.history.search

try {
          const response = await $b24.callMethod('im.notify.history.search', {
            SEARCH_TEXT: 'invoice',
            SEARCH_TYPE: 'tasks|task_update',
            SEARCH_DATE: '2026-03-03T16:52:29+01:00',
            LAST_ID: 1500,
            LIMIT: 20,
            CONVERT_TEXT: 'Y',
            GROUP_TAG: 'TASK|42',
          });
        
          const { result } = response.getData();
          console.log(result);
        } catch (error) {
          console.error(error);
        }

try {
            $response = $b24Service->core->call(
                'im.notify.history.search',
                [
                    'SEARCH_TEXT' => 'invoice',
                    'SEARCH_TYPE' => 'tasks|task_update',
                    'SEARCH_DATE' => '2026-03-03T16:52:29+01:00',
                    'LAST_ID' => 1500,
                    'LIMIT' => 20,
                    'CONVERT_TEXT' => 'Y',
                    'GROUP_TAG' => 'TASK|42',
                ]
            );
        
            $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.history.search',
            {
                SEARCH_TEXT: 'invoice',
                SEARCH_TYPE: 'tasks|task_update',
                SEARCH_DATE: '2026-03-03T16:52:29+01:00',
                LAST_ID: 1500,
                LIMIT: 20,
                CONVERT_TEXT: 'Y',
                GROUP_TAG: 'TASK|42',
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error().ex);
                } else {
                    console.log(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'im.notify.history.search',
            [
                'SEARCH_TEXT' => 'invoice',
                'SEARCH_TYPE' => 'tasks|task_update',
                'SEARCH_DATE' => '2026-03-03T16:52:29+01:00',
                'LAST_ID' => 1500,
                'LIMIT' => 20,
                'CONVERT_TEXT' => 'Y',
                'GROUP_TAG' => 'TASK|42',
            ]
        );
        
        if (!empty($result['error'])) {
            echo 'Error: ' . $result['error_description'];
        } else {
            var_dump($result['result']);
        }

Response Handling

HTTP Code: 200

{
            "result": {
                "chat_id": 77,
                "total_results": 1,
                "notifications": [
                    {
                        "id": 1500,
                        "chat_id": 77,
                        "author_id": 1,
                        "date": "2026-03-03T09:00:00+00:00",
                        "notify_type": 2,
                        "notify_module": "tasks",
                        "notify_event": "task_update",
                        "notify_tag": "TASK|42",
                        "notify_sub_tag": "",
                        "notify_title": "",
                        "setting_name": "tasks|task_update",
                        "text": "invoice",
                        "notify_read": "Y",
                        "params": null
                    }
                ],
                "users": [
                    {
                        "id": 1,
                        "active": true,
                        "name": "John Smith",
                        "first_name": "John",
                        "last_name": "Smith",
                        "work_position": "",
                        "color": "#1eb4aa",
                        "avatar": "https://example.bitrix24.com/upload/main/avatar.png",
                        "avatar_hr": "https://example.bitrix24.com/upload/main/avatar.png",
                        "gender": "M",
                        "birthday": "15-05",
                        "extranet": false,
                        "network": false,
                        "bot": false,
                        "connector": false,
                        "external_auth_id": "socservices",
                        "status": "online",
                        "idle": false,
                        "last_activity_date": "2026-03-04T15:04:20+01:00",
                        "mobile_last_date": false,
                        "desktop_last_date": false,
                        "absent": false,
                        "departments": [1],
                        "phones": {
                            "work_phone": "+11234567890",
                            "inner_phone": "22"
                        },
                        "bot_data": null,
                        "type": "user",
                        "website": "example.com",
                        "email": "john@example.com"
                    }
                ]
            },
            "time": {
                "start": 1760000000.0,
                "finish": 1760000000.1,
                "duration": 0.1,
                "processing": 0.04,
                "date_start": "2026-03-04T16:00:00+01:00",
                "date_finish": "2026-03-04T16:00:00+01:00",
                "operating_reset_at": 1760030000,
                "operating": 0
            }
        }

Returned Data

Name
Type

Description

result
object

Object containing the search result.

The structure of the object is described in detail below

time
time

Information about the request execution time

Result Object

Name `Type`	Description
chat_id `integer`	Identifier of the system notification chat
total_results `integer`	Total number of search results. This field is returned only on the first page of the search
notifications `array`	List of notifications. The structure of the object is described in detail below
users `array`	Users who authored the notifications The structure of the object is described in detail below

Notification Object

Name `Type`	Description
id `integer`	Identifier of the notification
chat_id `integer`	Identifier of the system notification chat
author_id `integer`	Identifier of the notification author
date `string`	Date and time of the notification in ISO 8601 format (RFC3339)
notify_type `integer`	Type of notification
notify_module `string`	Identifier of the notification module
notify_event `string`	Code of the notification event
notify_tag `string`	Notification tag
notify_sub_tag `string`	Additional notification tag
notify_title `string`	Title of the notification
setting_name `string`	Code of the setting in the format `MODULE\|EVENT`
text `string`	Text of the notification
notify_read `string`	Read status of the notification: `Y` or `N`
notify_buttons `string`	JSON keyboard for confirmation-type notifications. This field is not always present
params `object` `null`	Additional parameters of the notification

User Object

Name `Type`	Description
id `integer`	Identifier of the user
active `boolean`	User's active status
name `string`	User's full name
first_name `string`	User's first name
last_name `string`	User's last name
work_position `string`	User's position
color `string`	User's color in hex format
avatar `string`	Link to the avatar
avatar_hr `string`	Link to the high-resolution avatar
gender `string`	User's gender
birthday `string`	Birthday in `DD-MM` format or an empty string
extranet `boolean`	External user status
network `boolean`	Bitrix24 Network user status
bot `boolean`	Bot status
connector `boolean`	Open Channels user status
external_auth_id `string`	External authorization code
status `string`	User's status
idle `datetime`	User's idle date or `false`
last_activity_date `datetime`	User's last activity date
mobile_last_date `datetime`	User's last activity date in the mobile application or `false`
desktop_last_date `datetime`	User's last activity date in the desktop application or `false`
absent `datetime`	User's absence end date or `false`
departments `array`	Array of department identifiers
phones `object`	User's phones or `false` (detailed description)
bot_data `object`	Bot data or `null`
type `string`	User type
website `string`	User's website
email `string`	User's email

Phones Object

Name `Type`	Description
personal_mobile `string`	Mobile phone
inner_phone `string`	Internal phone

Error Handling

HTTP Status: 400

{
            "error": "SEARCH_TEXT_ERROR",
            "error_description": "SEARCH_TEXT can't be less than 3 symbols"
        }

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
`SEARCH_TEXT_ERROR`	SEARCH_TEXT can't be less than 3 symbols	This error occurs if `SEARCH_TYPE`, `SEARCH_DATE`, `SEARCH_TYPES`, `SEARCH_AUTHORS`, the pair `SEARCH_DATE_FROM` and `SEARCH_DATE_TO` are not specified, and the length of `SEARCH_TEXT` is less than `3`
`LAST_ID_STRING`	Last notification ID can't be string	The `LAST_ID` parameter contains a non-numeric 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 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

Delete Notification

Overview of Methods

Searching Notification History im.notify.history.search

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Result ObjectResult Object

Notification ObjectNotification Object

User ObjectUser Object

Phones ObjectPhones Object

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning