Event on Application Uninstallation: onAppUninstall
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:
basicWho can subscribe: any user
The ONAPPUNINSTALL event is triggered when an application is uninstalled.
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": "ONAPPUNINSTALL",
"data": {
"LANGUAGE_ID": "de",
"CLEAN": 1
},
"ts": "1466439714",
"auth": {
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"client_endpoint": "https://some-domain.bitrix24.com/rest/",
"member_id": "a223c6b3710f85df22e9377d6c4f7553",
"application_token": "51856fefc120afa4b628cc82d3935cce"
}
}
Request Parameters
Required parameters are marked with *
|
Name |
Description |
|
event* |
Event character code — |
|
data* |
Data about the uninstalled application. The structure is described below |
|
ts* |
Date and time of the event sent from the queue |
|
auth* |
Authorization and account data. The structure is described below |
Parameter data
|
Name |
Description |
|
LANGUAGE_ID* |
Set language: |
|
CLEAN* |
Value of the "Clear application data" option set by the user during uninstallation. Values: |
Parameter auth
|
Name |
Description |
|
domain* |
Address of the Bitrix24 account where the event occurred |
|
server_endpoint* |
Authorization server address for token renewal |
|
client_endpoint* |
Common path for API method calls to the account |
|
member_id* |
Unique identifier of the account |
|
application_token* |
Token for secure event handling |
When an application is uninstalled, all access permissions for the application to the API are revoked. Therefore, even though the event handler will receive authorization data, it can no longer use the API on behalf of the uninstalled application.