Event on Price Deletion CATALOG.PRICE.ON.DELETE

Scope: catalog

Who can subscribe: any user

The event occurs when a price 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 transmitted as a POST request

[
            'event' => 'CATALOG.PRICE.ON.DELETE',    
            'event_handler_id' => 1,
            'data' => [
                'FIELDS' => [
                    'ID' => 1,
                ],
            ],
            'ts' => 1714649632,
            'auth' => [
                'access_token' => 's6p6eclrvim6da22ft9ch94ekreb52lv',
                'expires_in' => 3600,
                'scope' => 'catalog',
                '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',
            ],
        ]

Parameters

Required parameters are marked with *

Name
type

Description

event*
string

Symbolic event code

event_handler_id*
integer

Event handler identifier

data*
object

Object with event data.

The structure is described below

ts*
integer

Timestamp of the event sent from the event queue

auth*
object

Object with authorization parameters and information about the account where the event occurred

Parameter data

Required parameters are marked with *

Name
type

Description

FIELDS*
object

Object with price properties.

The structure is described below

Parameter FIELDS

Required parameters are marked with *

Name
type

Description

ID*
catalog_price.id

Price identifier. You can retrieve all fields of the price by its identifier using the catalog.price.get method

Parameter auth

Required parameters are marked with *

Name
type

Description

access_token
string

Authorization token OAuth 2.0

expires_in
integer

Time in seconds until the token expires

scope*
string

Scope under which the event occurred

domain*
string

Address of Bitrix24 where the event occurred

server_endpoint*
string

Address of the Bitrix24 authorization server needed to refresh OAuth 2.0 tokens

status*
string

Status of the application that subscribed to this event:

client_endpoint*
string

Common path for REST API method calls for Bitrix24 where the event occurred

member_id*
string

Identifier of Bitrix24 where the event occurred

refresh_token
string

Token for extending authorization OAuth 2.0

application_token*
string

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 your exploration

Previous
When Updating a Price
Next
Overview of Methods