Docs for all releases
Page History
...
Panel | ||
---|---|---|
| ||
|
The Provisioning API provides a provides a mechanism for real-time integration with 3rd with 3rd party systems, including softswitches, gateways, and CRM systems. The The mechanism calls pre-defined handlers on an the occurrence of specific events in the system. The handlers are allowed to modify data, allow or forbid the action or simply process given event.
While Prior to that, JeraSoft Billing Core API and Management API provide utilities needed to receive requests from external systems. Now, you can configure the JeraSoft Billing platform to send requests to your 3rd party system.
sub-systems answer requests, Provisioning API pushes data as soon as an event occurs. For example, you can monitor the client's balance status via this functionality. Thus, when the client's balance is below zero, you can configure that the billing will system to send a notification to an external system a notification to avoid any disruptions to your organization's current processes.
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Tip The full list of Provisioning API parameters matches with CoreAPI and they are available upon individual request of your current clients. |
Handlers
...
Handlers
A typical handler should be configured as either HTTPS or HTTP with an URL of the script, which will get HTTP POST requests about each event occurrence.
Please avoid using the Script type of handlers, they are designed for internal usage within the system.
...
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Best practice example Here There is an example based on http https://hostname/handler-endpoint usage. 1.Open the Provisioning section and start creating a handler.
Find an example of the http://handler below:
|
Supported Events
The Provisioning API supports the following list of events:
- Clients
- clients.create
- clients.update
- clients.archive
- clients.delete
- clients.balance_zero
- clients.balance_notzero
- clients.custom_fields.update
- Accounts
- clients.accounts.create
- clients.accounts.update
- clients.accounts.delete
- Subscriptions
- clients.subscriptions.assign
- clients.subscriptions.activate
- clients.subscriptions.deactivate
- clients.subscriptions.renew
- clients.subscriptions.close
- Email Rates Manager
- email_rates_manager.import
- Import Manager
- importd.process_success
- importd.process_failed
Note | ||
---|---|---|
| ||
Please note that the |
Info | ||
---|---|---|
| ||
The |
Event Payload
Structure
During notification, the handler will be called with a JSON-formatted data payload. The payload has the following structure:
event
dt
- the date-time of the event in the ISO8601 format;events_id
- ID of the event occurred (helpful, when multiple events are handled by the same handler);object_id
- the entity, to which the event happened;
data
- data related to the specific event.
Example
Code Block |
---|
{
"event": {
"dt": "2000-01-01T00:00:00+00:00",
"events_id": "clients.update",
"object_id": 12
},
"data": {
"id": 12,
"field": "some-value"
}
} |
Data
The data provided within the notification depends on the specific type of event.
Events that represent basic status changes will not contain any additional data as the ID of the related entity is provided within the "event" key. Examples of such events are: clients.accounts.delete
, clients.archive
, clients.balance_notzero
, clients.balance_zero, etc.
For the rest of the events, the structure will match the respective CoreAPI method's structure. Please check the respective documentation within the system interface in the Integration/CoreAPI Docs section.
- create
- update
- delete
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Tip
|