Overview of Events When Working with Requisites
Events allow applications to respond to changes in near real-time. Notifications are available for the addition, modification, and deletion of requisites, bank details, and custom fields of requisites, as well as for the registration and deletion of addresses.
Detailed information on working with events is described in the article Concept and Benefits of Event Processing.
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.
Quick navigation: all events
How to Receive Events
You can subscribe to requisite events through the 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 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:
crmWho can subscribe: any user
|
Event |
Triggered |
|
When a requisite is added manually or via the crm.requisite.add method |
|
|
When a requisite is modified manually or via the crm.requisite.update method |
|
|
When a requisite is deleted manually or via the crm.requisite.delete method |
|
|
When an address is registered manually or via the crm.address.add method |
|
|
When an address is deleted manually or via the crm.address.delete method |
|
|
When a bank detail is added manually or via the crm.requisite.bankdetail.add method |
|
|
When a bank detail is modified manually or via the crm.requisite.bankdetail.update method |
|
|
When a bank detail is deleted manually or via the crm.requisite.bankdetail.delete method |
|
|
When a custom field of a requisite is added manually or via the crm.requisite.userfield.add method |
|
|
When a custom field of a requisite is modified manually or via the crm.requisite.userfield.update method |
|
|
When a custom field of a requisite is deleted manually or via the crm.requisite.userfield.delete method |
|
|
When the set of values for a custom field of list type is modified |