Response Codes for Non Messaging API Calls
Statuses
status | description |
---|---|
0 | OK |
Generic validation issues (1-99) | |
1 | Missing required parameter |
2 | Invalid parameter value |
3 | Authentication failed |
6 | Invalid Request |
4 | Account blocked |
5 | Operation Failed |
General business rules (100-199) | |
100 | Error defined in Description |
User specific (200-299) | |
200 | User does not exist |
201 | UserName already taken |
202 | Customer Account does not exist |
203 | User Details not Provided |
220 | User account needs to be activated |
204 | Gateway User Already Exists and Password does not match |
Customer specific (300-399) | |
300 | Customer does not exist |
301 | CustomerName Not Avaliable |
302 | Existing CustomerName Used |
320 | Insufficient credits |
Reseller specific (400-499) | |
400 | Reseller does not exist |
401 | ResellerName already taken |
420 | Reseller does not have rights to customer |
App Registration Errors | |
501 | No DeviceId Sent |
502 | No Matching AppPush Configured |
Virtually Number Management | |
601 | Number Not Allocated to Sender (Sender not Found) |
602 | Virtual Number not Found |
603 | Number Already Allocated to AppSender {0}, AppSender.Name |
604 | Number Not Allocated to Your Reseller Account |
605 | Number does not belong to AppSender |
606 | Invalid Number |
Sender Specific | |
701 | Sender not Found |
Contact Specific | |
801 | To Many Contact Records in Request |
Internal errors | |
9999 | Internal error |