This documentation relates to an earlier version of JeraSoft VCS.
View User Guide 3.26 or visit our current documentation home page.
In this article

Provisioning API provides a mechanism for real-time integration with 3rd party systems, including softswitches, gateways and CRM systems. The mechanism calls pre-defined handlers on an occurrence of specific events in the system. The handlers are allowed to modify data, allow or forbid the action or simply process given event. 

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.

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 send to an external system a notification to avoid any disruptions to your organization current processes.


The full list of Provisioning API parameters matches with CoreAPI and they are available upon individual request of your current clients.


There are two types of handlers that can be used: 

  • HTTP scripts, called via POST requests (used in most cases)
  • Local server scripts, called locally on the server (used in very specific cases)
Best practice example

Here is an example based on http://handler usage.

1. Open the Provisioning section and start creating a handler.

    1. Specify the name, type, and status.
    2. In the Event field, select the Clients Create event from the drop-down list.
    3. In the Task field, indicate http:// type and determine the port and method, for example,
    4. Click Apply.

Find an example of the http:// handler below:

from flask import Flask, request
import json
app = Flask(__name__)
@app.route("/api", methods=['GET', 'POST'])
def api():
    data = json.loads(
    return json.dumps(data)
if __name__ == "__main__":


The Provisioning API supports the following list of events:

  • create
  • update
  • delete
  • archive
  • custom fields update
  • balance became >=0
  • balance became <=0
  • create
  • update
  • delete
Clients Packages
  • assign
  • activate
  • deactivate
  • renew
  • close 


  • For more information about configuring and monitoring the hooks for Provisioning API, visit our respective article User Guide > System > Provisioning API.
  • If you need to process some of the actions that are not listed here, contact our support for a feature request. 
  • No labels