Billing request success
| Key | Description | Format |
| status | "success": indicates the correct recovery of information | STRING |
| scope | billing | STRING |
| billing | The proof of address in base64 encoding | STRING |
Response example:
{
"status": "success",
"scope": "billing",
"billing": "N0YXJ0eHJlZgo0OTg2MQolJUVPRgoKLS1ZS0xJNTYpPUlSeFdNUzEoYXJpOWI/UklzLkRXZ1dwUF9FLS0K"
}
Pending response :
| Key | Description | Format |
| status | "pending" : indicates that we are waiting for the operator | STRING |
| scope | billing | STRING |
Response example:
{
"status": "pending",
"scope": "billing",
}
Billing request error
| Key | Description | Format |
| status | "error": indicates that the request has failed | STRING |
| error_type | Error label detailed in the following table | STRING |
| error_id | Error code detailed in the following table | STRING(2) |
Error codes details (error_id):
| error_id | error_type | Description |
| 01 | invalid request | the request is not valid |
| 02 | invalid licence key | The license is not valid |
| 04 | invalid scope | Invalid scope |
| 18 | failed to retreive data from operator | No data received after OTP validation |
| 20 | OTP incorrect | OTP validation has not been completed |
| 21 | access denied | OTP validation declined |
| 30 | invalid or expired token | the token has expired |
| 99 | internal server error | Server error |
Response example:
{
"status": "error",
"error_type": "internal server error",
"error_id": "99"
}
Related to