Get Slot Settings for Resource booking.v1.resource.slots.list

Scope: booking

Who can execute the method: any user

The method booking.v1.resource.slots.list returns the configuration of time slots for the specified resource.

Method Parameters

Required parameters are marked with *

Name `type`	Description
resourceId* `integer`	Resource identifier. Can be obtained using the methods booking.v1.resource.add and booking.v1.resource.list

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 '{"resourceId":257}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/booking.v1.resource.slots.list

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"resourceId":257,"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/booking.v1.resource.slots.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(
            'booking.v1.resource.slots.list',
            { resourceId: 257 },
            (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('booking.v1.resource.slots.list', { resourceId: 257 }, '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('booking.v1.resource.slots.list', { resourceId: 257 }, 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(
                    'booking.v1.resource.slots.list',
                    [
                        'resourceId' => 257,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result->error()) {
                error_log($result->error());
            } else {
                echo 'Success: ' . print_r($result->data(), true);
            }
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error listing resource slots: ' . $e->getMessage();
        }

BX24.callMethod(
            "booking.v1.resource.slots.list",
            {
                resourceId: 257,
            },
            result => {
                if (result.error())
                    console.error(result.error());
                else
                    console.dir(result.data());
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'booking.v1.resource.slots.list',
            [
                'resourceId' => 257
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP status: 200

{
            "result": {
                "slots": [
                    {
                        "from": 100,
                        "id": 171,
                        "slotSize": 1,
                        "timezone": "Europe/Berlin",
                        "to": 300,
                        "weekDays": [
                            "Mon",
                            "Tue"
                        ]
                    }
                ]
            },
            "time": {
             "start": 1724068028.331234,
             "finish": 1724068028.726591,
             "duration": 0.3953571319580078,
             "processing": 0.13033390045166016,
             "date_start": "2025-01-21T13:47:08+01:00",
             "date_finish": "2025-01-21T13:47:08+01:00",
             "operating": 0
            }
        }

Returned Data

Name
type

Description

result
object

Root element of the response.

Contains an array of objects with information about the slots. The structure is described below

time
time

Information about the request execution time

Slot

Name `type`	Description
id `integer`	Identifier of the slot settings
from `integer`	Time from which slots are available for booking during the day. Value in the range from 0 to 1440. For example, `540` means booking is available from 9:00
to `integer`	End time of the slot in minutes. Value in the range from 0 to 1440, greater than or equal to the value of `from`. For example, `1080` means booking is available until 18:00
timezone `string`	Timezone relative to which the slot time is set
weekDays `array`	Array of available weekdays for the slot. Possible values: `"Mon"` — Monday `"Tue"` — Tuesday `"Wed"` — Wednesday `"Thu"` — Thursday `"Fri"` — Friday `"Sat"` — Saturday `"Sun"` — Sunday
slotSize `integer`	Duration of the slot in minutes

Error Handling

HTTP status: 400

{
            "error": 1009,
            "error_description": "Resource 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
`1009`	`Resource not found`	Resource with the specified `id` not found
`100`	`Could not find value for parameter`	Required parameter not provided

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

Remove slots for resource

Overview of Methods

Get Slot Settings for Resource booking.v1.resource.slots.list

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

SlotSlot

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning