OnOpenLineMessageDelete Chat Message Deletion Event
Scope:
imopenlinesWho can subscribe: any user
The OnOpenLineMessageDelete event triggers when a message is deleted in the open line chat.
Subscribe to the event can only be done through the application. The handler can only receive those events that are intended for the connector added by the application.
Events will not be sent to the application until the installation is complete. Check the application installation
What the handler receives
Data is transmitted in the form of a POST request
[
'event' => 'ONOPENLINEMESSAGEDELETE',
'eventId' => 1,
'data' => [
'CONNECTOR' => 'livechat',
'LINE' => 128,
'DATA' => [
[
'im' => [
'chat_id' => 1024,
'message_id' => 2056,
],
'message' => [
'id' => 2056,
],
'chat' => [
'id' => 1024
],
],
],
],
'ts' => 1714649632,
'auth' => [
'access_token' => 's6p6eclrvim6da22ft9ch94ekreb52lv',
'expires_in' => 3600,
'scope' => 'imopenlines',
'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 |
Description |
|
event* |
Symbolic event code |
|
eventId* |
Event identifier |
|
data* |
Object with event data |
|
ts* |
Timestamp of the event sent from the event queue |
|
auth* |
Object with authorization parameters and information about the account where the event occurred |
Data Parameter
Required parameters are marked with *
|
Name |
Description |
|
CONNECTOR* |
Connector identifier |
|
LINE* |
Open line identifier |
|
DATA* |
Object with chat data |
DATA Parameter
Required parameters are marked with *
|
Name |
Description |
|
im* |
Object with information about the deleted message in the chat:
|
|
message* |
Object with information about the message:
|
|
chat* |
Object with information about the chat:
|
Auth Parameter
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.