Developer Docs

Table of contents

API Errors

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"}

Errors for API 1.0

Common Errors
0no error
1invalid key
2 the user is blocked
3not enough parameters
4the requested function is not supported
5unknown error
6non-existent rate scale number is indicated
7invalid parameters
8not enough funds
9rate scale is inactive
10invalid sending time
11maximum number of messages processed simultaneously for sending has been exceeded
12maximum message package size is exceeded
SMS errors
20SMS not found
21invalid phone number
22no external SMS request ID
23SMS with such ID is already present
24invalid payload of request
25invalid originator
26SMS text is empty or too long
27Invalid external SMS ID
28invalid value of SMS duration time
29invalid task ID
30task not found
31the phone is already in the messaging list
32sender is not allowed
33direction is not allowed
34wrong OTP, code generation error
352way is not active for the account
36wrong 2way sender
Viber errors
40Viber message not found
41invalid phone number
43Viber message with this ID already exists
44invalid query payload
45Sender not registered
46empty or too long Viber message text
47invalid Viber message external I
48invalid value of Viber message duration
49invalid additional options of Viber messages
51phone number is already included to campaign
Number Verifier errors
60Number Verifier request not found
61invalid phone number
62no external Number Verifier request ID
63Number Verifier request with such ID already exists
64invalid query payload
65invalid Number Verifier request external ID
66phone number already exists in the request
Statistics generation Requests Errors
80invalid message_id (non numerical value)
81invalid message_type
82invalid source_type
83invalid status
84invalid country_id
85invalid clicks_comp
86invalid time frame
87invalid msisdn
88-89reserved for future use
Statistics file Requests Errors
90File not found
91File not ready
92Max files reached
93File is empty

Errors for API 2.0

Contacts and lists Errors
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

We use cookies (and other similar technologies) to collect data to improve your experience on our site. By using our website, you’re agreeing to the collection of data as described in our Website Data Collection Policy.