DEBUG API
There can be different reasons behind your API not working properly. We provide error codes according to the reason of API failure.
On hitting the API, if you face any issue, you can debug the API in the following manner:
- Check the response received on calling the API.
- If a Request ID is generated on hitting the API, this means that your SMS is successfully submitted to SMSGATEWAYHUB. If your message gets failed due to any problem with API you can find the reason for the failure in the failed API section.
- An error will be displayed instead of request ID* if your SMS is not submitted successfully. You can find the reason behind it in our list of error codes and remove the error accordingly.
API Error Code
| Erro Code | Description |
|---|---|
| 000 | Success |
| 001 | login details cannot be blank |
| 003 | sender cannot be blank |
| 004 | message text cannot be blank |
| 005 | message data cannot be blank |
| 006 | error: generic error description |
| 007 | username or password is invalid |
| 008 | account not active |
| 009 | account locked, contact your account manager |
| 010 | api restriction |
| 011 | ip address restriction |
| 012 | invalid length of message text |
| 013 | mobile numbers not valid |
| 014 | account locked due to spam message contact support |
| 015 | senderid not valid |
| 017 | groupid not valid |
| 018 | multi message to group is not supported |
| 019 | schedule date is not valid |
| 020 | message or mobile number cannot be blank |
| 021 | insufficient credits |
| 022 | invalid jobid |
| 023 | parameter missing |
| 024 | invalid template or template mismatch |
| 025 | {Field} can not be blank or empty |
| 026 | invalid date range |
| 027 | invalid optin user |
You may contact our support for any related query.