Event onCrmAddressUnregister
Scope:
crmWho can subscribe:
any user
The event onCrmAddressUnregister is triggered when an address is deleted.
Events will not be sent to the application until the installation is complete. Check the application installation
What the handler receives
Data is sent as a POST request
[
'event' => 'onCrmAddressUnregister',
'data' => [
'FIELDS' => [
'TYPE_ID' => 1,
'ENTITY_TYPE_ID' => 8,
'ENTITY_ID' => 1,
'ANCHOR_ID' => 17192,
'ANCHOR_TYPE_ID' => 3,
],
],
'ts' => '1466439714',
'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',
],
]
Required parameters are marked with *
|
Parameter |
Description |
|
event* |
Symbolic event code. In this case, it is |
|
data* |
Array with the data of the deleted address |
|
ts* |
Date and time the event was sent from the event queue |
|
auth* |
Authorization parameters and information about the account where the event occurred |
Parameter data[]
Required parameters are marked with *
|
Parameter |
Description |
|
FIELDS* |
Array with the fields of the deleted address |
Parameter FIELDS[]
Required parameters are marked with *
|
Parameter |
Description |
|
TYPE_ID* |
Identifier of the address type. Enumeration element "Address Type". The enumeration elements "Address Type" are returned by the method crm.enum.addresstype |
|
ENTITY_TYPE_ID* |
Identifier of the parent object's type. Object type identifiers are returned by the method crm.enum.ownertype. Addresses can only be linked to Requisites (which are linked to companies or contacts) or Leads. For backward compatibility, the ability to link Addresses to Contacts or Companies is retained. However, this linkage is only possible on some older accounts where the old address handling mode was specifically enabled by technical support. |
|
ENTITY_ID* |
Identifier of the parent object |
|
ANCHOR_ID* |
Identifier of the main parent object. This field is for internal use. The value is automatically filled when the address is added. This field contains the identifier of the parent object of the requisite (company or contact) if the address is linked to a requisite. If the address is linked to a lead, this value will be the lead identifier. |
|
ANCHOR_TYPE_ID* |
Identifier of the type of the main parent object. This field is for internal use. The value is automatically filled when the address is added. Object type identifiers are returned by the method crm.enum.ownertype. This field contains the identifier of the type of the parent object of the requisite (company or contact) if the address is linked to a requisite. If the address is linked to a lead, this value will be the lead type identifier. |
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
- Event onCrmAddressRegister
- Event onCrmRequisiteAdd
- Event onCrmRequisiteUpdate
- Event onCrmRequisiteDelete
- Event when adding a custom field of a requisite onCrmRequisiteUserFieldAdd
- Event on changing the set of values for a custom list-type field onCrmRequisiteUserFieldSetEnumValues
- Event on changing user field of the requisite onCrmRequisiteUserFieldUpdate
- Event onCrmRequisiteUserFieldDelete
- Event on adding bank details onCrmBankDetailAdd
- Event onCrmBankDetailUpdate
- Event onCrmBankDetailDelete