Event onCrmContactUserFieldUpdate
Scope:
crmWho can subscribe: any user
The event onCrmContactUserFieldUpdate is triggered when a custom field is changed for contacts.
Events will not be sent to the application until the installation is complete. Check the application installation
What the handler receives
Data is transmitted as a POST request
{
"event": "ONCRMCONTACTUSERFIELDUPDATE",
"event_handler_id": "15",
"data": {
"FIELDS": {
"ID": "554",
"ENTITY_ID": "CRM_CONTACT",
"FIELD_NAME": "UF_CRM_1724771514"
}
},
"ts": "1724775198",
"auth": {
"access_token": "s6p6eclrvim6da22ft9ch94ekreb52lv",
"expires_in": "3600",
"scope": "crm",
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"status": "F",
"client_endpoint": "https://some-domain.bitrix24.com/rest/",
"member_id": "a223c6b3710f85df22e9377d6c4f7553",
"refresh_token": "4s386p3q0tr8dy89xvmt96234v3dljg8",
"application_token": "51856fefc120afa4b628cc82d3935cce"
}
}
|
Parameter |
Description |
|
event |
Symbolic event code. In this case — |
|
event_handler_id |
Identifier of the event handler |
|
data |
Object containing information about the changed custom field Contains a single key |
|
data.FIELDS |
Object containing information about the fields of the changed custom field The structure is described below |
|
ts |
Date and time the event was sent from the event queue |
|
auth |
Object containing authorization parameters and information about the account where the event occurred. The structure is described below |
Parameter FIELDS
|
Parameter |
Description |
|
ID |
Identifier of the changed custom field |
|
ENTITY_ID |
Type of CRM object to which the custom field is attached. In this case — |
|
FIELD_NAME |
Code of the changed custom field |
Parameter auth
Required parameters are marked with *
|
Name |
Description |
|
access_token |
Authorization token OAuth 2.0 |
|
expires_in |
Time in seconds until the token expires |
|
scope* |
Scope under which the event occurred |
|
domain* |
Address of Bitrix24 where the event occurred |
|
server_endpoint* |
Address of the Bitrix24 authorization server needed to refresh OAuth 2.0 tokens |
|
status* |
Status of the application that subscribed to this event:
|
|
client_endpoint* |
Common path for REST API method calls for Bitrix24 where the event occurred |
|
member_id* |
Identifier of Bitrix24 where the event occurred |
|
refresh_token |
Token for extending authorization OAuth 2.0 |
|
application_token* |
Token for secure event handling |
Authorization tokens are not always passed to the event handler. If the hit that initiated the event could not be linked to a specific Bitrix24 user, the tokens are not passed. Always check the contents of the auth key in the code.
It is recommended to store tokens obtained earlier during the application installation. Use them when working with the application interface in the form of embeds, widgets, and so on.
Continue exploring
- Overview of Events When Working with Custom Contact Fields
- Event onCrmContactUserFieldAdd
- Event on changing the set of values for a custom list-type field onCrmContactUserFieldSetEnumValues
- Event onCrmContactUserFieldDelete