OnOpenLineMessageDelete Chat Message Deletion Event
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.
Scope:
imopenlinesWho can subscribe: any user
The OnOpenLineMessageDelete event triggers when a message is deleted in an open line chat.
Subscribe to the event can only be done through the application. Only those events intended for the connector added by the application can be received in the handler.
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": "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"
}
}
Required parameters are marked with *
|
parameter |
Description |
|
event* |
Symbolic code of the event. In this case — |
|
eventId* |
Event identifier |
|
data* |
An object containing event data. The structure is described below |
|
ts* |
Date and time of the event 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 data
|
parameter |
Description |
|
CONNECTOR* |
Connector identifier |
|
LINE* |
Identifier of the open line |
|
DATA* |
An array of objects with deleted message data. The object structure is described below |
Array Element DATA
Each array element DATA is an object with the following structure:
|
parameter |
Description |
|
im* |
An object with information about a deleted message in a chat. The structure is described below |
|
message* |
An object with information about a message. The structure is described below |
|
chat* |
An object with information about a chat. The structure is described below |
Parameter im
|
parameter |
Description |
|
chat_id* |
Identifier of the chat |
|
message_id* |
Identifier of the message |
Parameter message
|
parameter |
Description |
|
id* |
Identifier of the message |
Parameter chat
|
parameter |
Description |
|
id* |
Identifier of the chat |
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.