Event on Application Payment onAppPayment
Scope:
basicWho can subscribe: any user
The onAppPayment event is triggered when an application is paid for.
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": "ONAPPPAYMENT",
"data": {
"CODE": "bitrix.gds_company",
"VERSION": 1,
"STATUS": "S",
"PAYMENT_EXPIRED": "N",
"DAYS": 28,
"LANGUAGE_ID": "en"
},
"ts": "1466439714",
"auth": {
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"client_endpoint": "https://some-domain.bitrix24.com/rest/"
}
}
Request Parameters
Required parameters are marked with *
|
Name |
Description |
|
event* |
Symbolic event code — |
|
data* |
Payment data. The structure is described below |
|
ts* |
Date and time of event dispatch from the queue |
|
auth* |
Authorization and account data. The structure is described below |
Parameter data
Required parameters are marked with *
|
Name |
Description |
|
|
CODE* |
Application code |
|
|
VERSION* |
Installed application version |
|
|
STATUS* |
Application status. Possible values:
|
|
|
PAYMENT_EXPIRED* |
[Y |
N] Flag indicating whether the paid period or trial period has expired |
|
DAYS* |
Number of days remaining until the end of the paid period or trial period |
|
|
LANGUAGE_ID* |
Installed language: |
Parameter auth
Required parameters are marked with *
|
Name |
Description |
|
domain* |
Bitrix24 account address |
|
server_endpoint* |
Authorization server address for token refresh |
|
client_endpoint* |
Common path for API method calls to the account |
|
member_id* |
Unique account identifier |
Continue Learning
- Event Handler
- Register a new event handler event.bind
- Show information about the app app.info
- Event After Successful Application Installation OnAppInstall
- Event on Receiving Permission for Using onAppMethodConfirm Methods
- Event onUserAdd
- Event on Application Uninstallation: onAppUninstall