Overview of Events When Working with Waitlist Records
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.
Events allow applications to respond to changes in almost real-time: receiving notifications about the creation, updating, and deletion of records in the waitlist.
Detailed information on working with events is described in the article Concept and Benefits of Event Processing.
Quick navigation: all events
How to Receive Events
You can subscribe to waitlist entry events through:
- outgoing webhook
- application and the method event.bind
An example of a handler code for the event is described in the article How to Test Your Handler for Processing Bitrix24 Events.
Server Availability for Sending and Receiving Events
The event handler server must be accessible from the outside. To configure the accessibility of the event handler server and application, refer to the article Required network access.
For cloud Bitrix24, no additional configuration is required. For on-premise Bitrix24, configure accessibility on the server or hosting according to the article Required network access.
Overview of Events
Scope:
bookingWho can subscribe: any user
|
Event |
Triggered By |
|
When a waitlist entry is created manually or by the methods booking.v1.waitlist.add, booking.v1.waitlist.createfrombooking |
|
|
When a waitlist entry is changed manually or by the method booking.v1.waitlist.update |
|
|
When a waitlist entry is deleted manually or by the method booking.v1.waitlist.delete |