BSG uses standard HTTP status codes to indicate the success or failure of an API query.
In response to an API query, you may receive an error message, which may indicate that something is wrong with your query or on our part.
In case of an error, the response body includes a json format response telling you exactly what is wrong.
Example:
{"error":"40","errorDescription":"Message not found"}
| 0 | no error |
|---|---|
| 1 | invalid key |
| 2 | the user is blocked |
| 3 | not enough parameters |
| 4 | the requested function is not supported |
| 5 | unknown error |
| 6 | non-existent rate scale number is indicated |
| 7 | invalid parameters |
| 8 | not enough funds |
| 9 | rate scale is inactive |
| 10 | invalid sending time |
| 11 | maximum number of messages processed simultaneously for sending has been exceeded |
| 12 | maximum message package size is exceeded |
| 20 | SMS not found |
|---|---|
| 21 | invalid phone number |
| 22 | no external SMS request ID |
| 23 | SMS with such ID is already present |
| 24 | invalid payload of request |
| 25 | invalid originator |
| 26 | SMS text is empty or too long |
| 27 | Invalid external SMS ID |
| 28 | invalid value of SMS duration time |
| 29 | invalid task ID |
| 30 | task not found |
| 31 | the phone is already in the messaging list |
| 32 | sender is not allowed |
| 33 | direction is not allowed |
| 34 | wrong OTP, code generation error |
| 35 | 2way is not active for the account |
| 36 | wrong 2way sender |
| 40 | Viber message not found |
|---|---|
| 41 | invalid phone number |
| 43 | Viber message with this ID already exists |
| 44 | invalid query payload |
| 45 | Sender not registered |
| 46 | empty or too long Viber message text |
| 47 | invalid Viber message external I |
| 48 | invalid value of Viber message duration |
| 49 | invalid additional options of Viber messages |
| 51 | phone number is already included to campaign |
| 60 | Number Verifier request not found |
|---|---|
| 61 | invalid phone number |
| 62 | no external Number Verifier request ID |
| 63 | Number Verifier request with such ID already exists |
| 64 | invalid query payload |
| 65 | invalid Number Verifier request external ID |
| 66 | phone number already exists in the request |
| 80 | invalid message_id (non numerical value) |
|---|---|
| 81 | invalid message_type |
| 82 | invalid source_type |
| 83 | invalid status |
| 84 | invalid country_id |
| 85 | invalid clicks_comp |
| 86 | invalid time frame |
| 87 | invalid msisdn |
| 88-89 | reserved for future use |
| 90 | File not found |
|---|---|
| 91 | File not ready |
| 92 | Max files reached |
| 93 | File is empty |
| Invalid phone number format | |
|---|---|
| Contact not found | |
| The phone number already exists in the user’s Contact Book | |
| Number of available fields exceeded | |
| Invalid contact field format | |
| Invalid date field format | |
| Invalid numeric field format | |
| A field with such name already exists | |
| A contact group with such name already exists | |
| Invalid contact list | |
| Contact group not found | |
| Invalid contact group | |
| Blocked contact not found | |
| Campaign not found | |
| Action not available for this account type | |
| Field not found | |
| Invalid operator for contact search | |
| Invalid search value format |
| Unavailable for your account status | |
|---|---|
| Tariff not found | |
| Invalid phone number format | |
| Invalid list of the phone number | |
| All numbers are in the stop list | |
| Contacts group is not found | |
| Empty groups | |
| Campaign not found | |
| Invalid campaign status |
|
| Invalid country specified |
|---|---|
| Name registration is not allowed for the specified country |
| Tariff not found | |
|---|---|
| Operator not found | |
| Operator price not found |