Flow #
The MP APIs system currently only shows support for functions such as orders, traffic,activation-code, and alarms
Flow general #
In this chapter, some typical flows will be described.
A typical flow #
The apis flow of typical process for successfully querying the status of an order is as follows：
| No. of step | description | API used |
|---|---|---|
| 1 | select interface | /mp-api/api/esim/queryOrderStatus |
| 2 | generate a signature according to the signature algorithm specification | Client writing algorithm program |
| 3 | make API calls using the generated signature | /mp-api/api/esim/queryOrderStatus |
Customer order #
To support partner’s 2C business the MP system provide an API to get the activation code and create a releated-order in MP side directly so the partner can switch(ON/OFF)the order to enbable/disable the services(sms,data,voice) later.
Alarm callback flow #
MP system also provide a feature to notify customer concerned information so the partner can manage their own business depending on the alarm callback,in alarm callback process, the MP system acts as a client to send a request to the webhook URL.
| No. of step | description | API used |
|---|---|---|
| 1 | Prepare your webhook URL and the setting the URL by calling the API | The interface must be a POST type |
| 2 | save your POST interface to the configuration table of your MP system by calling | /mp-api/api/esim/saveAlarmCallbackInterface |
| 3 | When the alarm triggered MP send the notification to the webhook URL | WebHook URL |
| 4 | Receiving the notification of the alarm from MP and handle business accordingly | NA |
