Error codes
Last update: 4 days ago by Irais Aguirre
When code is different from 0, the message was not sent. Check the following table to identify the cause and the corrective action:
| Code | Message | What to do |
|---|---|---|
| -10 | Message is too long | The text exceeds the limit; shorten the message. |
| -11 | The message cannot be empty | Make sure message is not empty and does not contain invalid characters. |
| -20 | The client was not found | The API key is not active or does not exist; contact support. |
| -21 | Access denied, verify credentials | Invalid token or missing claim; request a new token. |
| -30 | Insufficient funds | Insufficient account balance; top up your balance. |
| -40 | Carrier/country incorrect | Verify the country code (country) and the carrier (carrier). |
| -45 | Dial incorrect for carrier | The shortcode (dial) does not exist for the specified carrier. |
| -46 | Dial not associated to account | That shortcode is not enabled for your account; contact support. |
| -50 | Service unavailable | Transient error; retry after a few seconds. |
| -55 | No profiling enabled | Send the carrier field explicitly. |
| -60 | Account cannot use mask | Masks are not enabled for your account; contact support. |
| -72 | Incorrect schedule date | The schedule date is earlier than the current date. |
| -75 | Incorrect msisdn structure | The number has an invalid format or length for the country. |
| -76 | Incorrect parameter | One of the parameters has an invalid value; review the request. |
| -77 | Data encoding not supported | The encoding in dataCoding is not supported. |
| -79 | Bad request | Generic validation error; review the dial, msisdn, and dlr/optionals fields. |
| -80 | Incorrect tag structure | The tag field has an invalid format. |
| -81 | Incorrect schedule structure | The schedule field is not in the correct ISO 8601 format. |
| -86 | Country not supported | The specified country is not enabled in your configuration. |
| -87 | Carrier not supported | The specified carrier is not enabled in your configuration. |
| -109 | Balance limit reached | The spending limit configured for your account was reached. |
| -111 | No API submission permissions | Your account does not have permission to send via API; contact support. |
HTTP errors
| HTTP | Cause | What to do |
|---|---|---|
| 401 | Invalid, expired, or wrong-realm token | Request a new token (Step 1). |
| 500 | Internal server error | Retry with exponential backoff; if it persists, contact support. |