How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bitrix24 Online Booking API

The Online Booking API from Bitrix24 — 38 operation(s) for online booking.

Bitrix24 Online Booking API is one of 36 APIs that Bitrix24 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Online Booking. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 38 operations across 38 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://{portal}.bitrix24.com/rest, https://{host}/rest.

38 operations 38 paths 3 schemas 38 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://{installation}.bitrix24.com/rest/
Authentication
API Key, OAuth 2.0
License
Resource Areas
1

Authentication & Security 2

Bitrix24 Online Booking API declares 2 security schemes for authenticating requests. An API key is passed in the query as auth (AccessToken). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 45 scopes. By default, every request must be authenticated.

  • AccessToken — OAuth 2.0 accesstoken or incoming webhook token
  • OAuth2 — OAuth 2.0 authorization

Paths & Operations 38

Across 38 paths, the API surfaces 38 operations — 38 POST. Each is listed below with its method, path, parameters, and response codes.

Online Booking 38
POST
/booking.v1.booking.add
Add Booking booking.v1.booking.add
booking_v1_booking_add body → 2004XX
POST
/booking.v1.booking.client.list
Get the list of booking clients booking.v1.booking.client.list
booking_v1_booking_client_list body → 2004XX
POST
/booking.v1.booking.client.set
Add Clients to Booking booking.v1.booking.client.set
booking_v1_booking_client_set body → 2004XX
POST
/booking.v1.booking.client.unset
Remove clients from booking booking.v1.booking.client.unset
booking_v1_booking_client_unset body → 2004XX
POST
/booking.v1.booking.createfromwaitlist
Create a Booking from the Waitlist booking.v1.booking.createfromwaitlist
booking_v1_booking_createfromwaitlist body → 2004XX
POST
/booking.v1.booking.delete
Delete Booking booking.v1.booking.delete
booking_v1_booking_delete body → 2004XX
POST
/booking.v1.booking.externalData.list
Get Booking Connections booking.v1.booking.externalData.list
booking_v1_booking_externalData_list body → 2004XX
POST
/booking.v1.booking.externalData.set
Set Connections for Booking booking.v1.booking.externalData.set
booking_v1_booking_externalData_set body → 2004XX
POST
/booking.v1.booking.externalData.unset
Remove connections for booking booking.v1.booking.externalData.unset
booking_v1_booking_externalData_unset body → 2004XX
POST
/booking.v1.booking.get
Get Information About Booking booking.v1.booking.get
booking_v1_booking_get body → 2004XX
POST
/booking.v1.booking.list
Get the list of bookings booking.v1.booking.list
booking_v1_booking_list body → 2004XX
POST
/booking.v1.booking.update
Update Booking booking.v1.booking.update
booking_v1_booking_update body → 2004XX
POST
/booking.v1.clienttype.list
Get a list of client types booking.v1.clienttype.list
booking_v1_clienttype_list body → 2004XX
POST
/booking.v1.resource.add
Add a New Resource booking.v1.resource.add
booking_v1_resource_add body → 2004XX
POST
/booking.v1.resource.delete
Delete Resource booking.v1.resource.delete
booking_v1_resource_delete body → 2004XX
POST
/booking.v1.resource.get
Get resource booking.v1.resource.get
booking_v1_resource_get body → 2004XX
POST
/booking.v1.resource.list
Get the list of resources booking.v1.resource.list
booking_v1_resource_list body → 2004XX
POST
/booking.v1.resource.slots.list
Get Slot Settings for Resource booking.v1.resource.slots.list
booking_v1_resource_slots_list body → 2004XX
POST
/booking.v1.resource.slots.set
Set Slots for Resource booking.v1.resource.slots.set
booking_v1_resource_slots_set body → 2004XX
POST
/booking.v1.resource.slots.unset
Remove slots for resource booking.v1.resource.slots.unset
booking_v1_resource_slots_unset body → 2004XX
POST
/booking.v1.resource.update
Update resource booking.v1.resource.update
booking_v1_resource_update body → 2004XX
POST
/booking.v1.resourceType.add
Add a New Resource Type booking.v1.resourceType.add
booking_v1_resourceType_add body → 2004XX
POST
/booking.v1.resourceType.delete
Delete Resource Type booking.v1.resourceType.delete
booking_v1_resourceType_delete body → 2004XX
POST
/booking.v1.resourceType.get
Get Resource Type booking.v1.resourceType.get
booking_v1_resourceType_get body → 2004XX
POST
/booking.v1.resourceType.list
Get a list of resource types booking.v1.resourceType.list
booking_v1_resourceType_list body → 2004XX
POST
/booking.v1.resourceType.update
Update Resource Type booking.v1.resourceType.update
booking_v1_resourceType_update body → 2004XX
POST
/booking.v1.waitList.externalData.list
Get External Data Links for Waitlist Entry booking.v1.waitList.externalData.list
booking_v1_waitList_externalData_list body → 2004XX
POST
/booking.v1.waitlist.add
Add to waitlist booking.v1.waitlist.add
booking_v1_waitlist_add body → 2004XX
POST
/booking.v1.waitlist.client.list
Get the list of clients for the waitlist booking.v1.waitlist.client.list
booking_v1_waitlist_client_list body → 2004XX
POST
/booking.v1.waitlist.client.set
Add Clients to the Waitlist Record in booking.v1.waitlist.client.set
booking_v1_waitlist_client_set body → 2004XX
POST
/booking.v1.waitlist.client.unset
Remove clients from the waitlist entry booking.v1.waitlist.client.unset
booking_v1_waitlist_client_unset body → 2004XX
POST
/booking.v1.waitlist.createfrombooking
Create a waitlist entry from booking using booking.v1.waitlist.createfrombooking
booking_v1_waitlist_createfrombooking body → 2004XX
POST
/booking.v1.waitlist.delete
Delete Entry from the Waitlist booking.v1.waitlist.delete
booking_v1_waitlist_delete body → 2004XX
POST
/booking.v1.waitlist.externalData.set
Set Connections for Recording in the Waitlist booking.v1.waitlist.externalData.set
booking_v1_waitlist_externalData_set body → 2004XX
POST
/booking.v1.waitlist.externalData.unset
Remove connections for the waitlist record booking.v1.waitlist.externalData.unset
booking_v1_waitlist_externalData_unset body → 2004XX
POST
/booking.v1.waitlist.get
Get a Record from the Waitlist booking.v1.waitlist.get
booking_v1_waitlist_get body → 2004XX
POST
/booking.v1.waitlist.list
Get a list of records from the waitlist booking.v1.waitlist.list
booking_v1_waitlist_list body → 2004XX
POST
/booking.v1.waitlist.update
Update a record in the waitlist booking.v1.waitlist.update
booking_v1_waitlist_update body → 2004XX

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are BitrixTime (8 properties), BitrixResponse (4 properties), BitrixError (2 properties). Each schema is shown below with its type and property counts.

BitrixError
object
Bitrix24 REST API error response
2 properties 2 required
BitrixTime
object
Request execution time information
8 properties
BitrixResponse
object
Standard Bitrix24 REST API response
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bitrix24-online-booking-api-openapi.yml Raw ↑

Other APIs Bitrix24 publishes across the network.

Bitrix24 REST API
Bitrix24 BIconnector API
Bitrix24 Business Processes API
Bitrix24 Calendar API
Bitrix24 Chatbots API
Bitrix24 Chats API
Bitrix24 Company Structure API
Bitrix24 CoPilot / AI API
Bitrix24 CRM API
Bitrix24 Data Storage API
Bitrix24 Deprecated Methods API
Bitrix24 Document Generator API
Where this information came from

This is an independent, third-party profile of Bitrix24 Online Booking API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.