The full definition of the response is documented in this table below.
When responding, the REST API will make use of the appropriate and relevant HTTP status code to describe the nature of the result. For non-200 response codes, not all of the fields described in Outer Response, RESULT Item, and RESULT_DETAIL Item might be present.
HTTP Status Code | Description |
---|---|
200 | All OK. |
400 | Bad Request – The request is invalid and was not understood by the API. |
401 | Unauthorized – Header “Authorization” missing, invalid, or revoked; and / or, your host IP is not in the authorized IPs list. |
403 | The request contains invalid or illegal values. |
404 | Not Found – The endpoint on which the request was sent to, does not exist, or does not implement the API requested. |
405 | Method Not Allowed – If the endpoint received a request using an HTTP method (ex. GET instead of POST) that is not allowed by that endpoint. |
413 | Request entity was too large. Maximum size of 32,768 bytes allowed. |
415 | Unsupported Media Type – If the request was in a content-type not supported by the endpoint (ex. text/plain instead of application/json). |
429 | Too many requests (Throttling). |
500 | Internal Server Error. |
The body of the response contains a JSON-structured reply detailing the outcome of your request. For non -HTTP 200 response codes, not all the fields described in Outer Response, RESULT Item, and RESULT_DETAIL Item may be present.
Key | Type | Optional | Description |
---|---|---|---|
api_job_id | String | N | A UUID identifying the life-cycle of this individual request / response, along with any future pending tasks relating to this request. Useful for error investigations and chaining. |
client_job_id | String | Y | If applicable, the job_id supplied by the client from the request is echoed back here. |
results | RESULT[] | Y | If applicable, this array contains results for each destination (see RESULT Object). |
Key | Type | Optional | Description |
---|---|---|---|
{destination_msisdn} | RESULT_DETAIL | N | If available (since an invalid request might not have this information), each RESULT item will have each destination MSISDN here as a key, and its details as a value (see Request Body » SMS_CONTENT). |
Key | Type | Optional | Description |
---|---|---|---|
message_id | String | Y | If the request was successful, a unique ID generated by the API for the message to this particular destination is returned here. |
custom_id | String | Y | If supplied, the custom_id supplied by the client from the request is echoed here. |