Get a list of offline events event.offline.list

Who can execute the method: any user

The method event.offline.list is used to read the current queue without making changes to its state, unlike event.offline.get. The availability of offline events can be checked through the feature.get method.

The method works only in the context of application authorization application.

Method Parameters

Required parameters are marked with *

Name
type

Description

filter
array

Record filter. By default, all records are returned without filtering. Filtering is supported by the fields: ID, TIMESTAMP_X, EVENT_NAME, MESSAGE_ID, PROCESS_ID, ERROR with standard operations like =, >, <, <=, and so on

order
array

Record sorting. Sorting is supported by the same fields as in the filter, and an array of the form `[field=>ASC

DESC]is accepted. By default —[ID:ASC]`

start
integer

This parameter is used to manage pagination.

The page size of results is always static: 50 records.

To select the second page of results, you need to pass the value 50. To select the third page of results — the value 100, and so on.

The formula for calculating the start parameter value:

start = (N-1) * 50, where N is the desired page number

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{
            "filter": {
                "ERROR": 0
            },
            "order": {
                "ID": "DESC"
            },
            "auth": "**put_access_token_here**"
        }' \
        https://**put_your_bitrix24_address**/rest/event.offline.list
        
// callListMethod: Retrieves all data at once. Use only for small selections (< 1000 items) due to high memory usage.
        
        try {
          const response = await $b24.callListMethod(
            'event.offline.list',
            {
              "filter": {
                "ERROR": 0
              },
              "order": {
                "ID": "DESC"
              }
            },
            (progress) => { console.log('Progress:', progress) }
          )
          const items = response.getData() || []
          for (const entity of items) { console.log('Entity:', entity) }
        } catch (error) {
          console.error('Request failed', error)
        }
        
        // fetchListMethod: Retrieves data in parts using an iterator. Use it for large data volumes to optimize memory usage.
        
        try {
          const generator = $b24.fetchListMethod('event.offline.list', { "filter": { "ERROR": 0 }, "order": { "ID": "DESC" } }, 'ID')
          for await (const page of generator) {
            for (const entity of page) { console.log('Entity:', entity) }
          }
        } catch (error) {
          console.error('Request failed', error)
        }
        
        // callMethod: Manually controls pagination through the start parameter. Use it for precise control of request batches. For large datasets, it is less efficient than fetchListMethod.
        
        try {
          const response = await $b24.callMethod('event.offline.list', { "filter": { "ERROR": 0 }, "order": { "ID": "DESC" } }, 0)
          const result = response.getData().result || []
          for (const entity of result) { console.log('Entity:', entity) }
        } catch (error) {
          console.error('Request failed', error)
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'event.offline.list',
                    [
                        'filter' => [
                            'ERROR' => 0,
                        ],
                        'order' => [
                            'ID' => 'DESC',
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result->error()) {
                error_log($result->error());
                echo 'Error: ' . $result->error();
            } else {
                echo 'Success: ' . print_r($result->data(), true);
            }
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error fetching offline events: ' . $e->getMessage();
        }
        
BX24.callMethod(
            "event.offline.list",
            {
                "filter": {
                    "ERROR": 0
                },
                "order": {
                    "ID": "DESC"
                }
            },
            function(result)
            {
                if(result.error())
                    console.error(result.error());
                else
                    console.dir(result.data());
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'event.offline.list',
            [
                'filter' => [
                    'ERROR' => 0
                ],
                'order' => [
                    'ID' => 'DESC'
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        

Response Handling

HTTP status: 200

{
            "result": [
                {
                    "ID": "2",
                    "TIMESTAMP_X": "2024-07-18T12:32:31+02:00",
                    "EVENT_NAME": "ONCRMCOMPANYADD",
                    "EVENT_DATA": false,
                    "EVENT_ADDITIONAL": false,
                    "MESSAGE_ID": "2",
                    "PROCESS_ID": "",
                    "ERROR": "0"
                },
                {
                    "ID": "1",
                    "TIMESTAMP_X": "2024-07-18T12:32:31+02:00",
                    "EVENT_NAME": "ONCRMLEADADD",
                    "EVENT_DATA": false,
                    "EVENT_ADDITIONAL": false,
                    "MESSAGE_ID": "1",
                    "PROCESS_ID": "",
                    "ERROR": "0"
                }
            ],
            "total": 2,
            "time": {
                "start": 1721299537.90267,
                "finish": 1721299538.02201,
                "duration": 0.11934018135070801,
                "processing": 0.0029511451721191406,
                "date_start": "2024-07-18T12:45:37+02:00",
                "date_finish": "2024-07-18T12:45:38+02:00",
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
object

Root element of the response

total
integer

Total number of records found

time
time

Information about the execution time of the request

Error Handling

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