Overview of Events in Online Store Management
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 the online store almost in real-time: receiving notifications about the creation and deletion of orders, payments, shipments, and property values of orders.
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 online store events through:
- outgoing webhook
- application and the event.bind method
An example of a handler code for an event is described in the article How to Test Your Handler for Bitrix24 Event Processing.
Limitations and Features of Event Delivery
- Events are not sent to the application until the application installation is complete. More details can be found in the article Check Application Installation.
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:
saleWho can subscribe: any user
|
Event |
Triggered |
|
At the end of order saving |
|
|
Before order deletion |
|
|
After saving order property value |
|
|
After saving payment |
|
|
After saving shipment |
|
|
After saving order |
|
|
When order property value is deleted |
|
|
When payment is deleted from the database |
|
|
When shipment is deleted from the database |
|
|
When order is deleted from the database |