Standard Error Codes
All errors that may come across in ValueFirst XML API are listed below
| Error Code | Description |
| General | |
| 52992 | Username / Password incorrect |
| 57089 | Contract expired |
| 57090 | User credit expired |
| 57091 | User disabled |
| 65280 | Service is temporarily unavailable |
| 65535 | The specified message does not conform to DTD |
| 0 | SMS submitted success NO Error (Not returned in ValueFirst XML API ) |
| Message Post | |
| 28673 | Destination number not numeric |
| 28674 | Destination number empty |
| 28675 | Sender address empty |
| 28676 | Template mismatch |
| 28677 | UDH is invalid / SPAM message |
| 28678 | Coding is invalid |
| 28679 | SMS text is empty |
| 28680 | Invalid sender ID |
| 28681 | Invalid message, Duplicate message, Submit failed |
| 28682 | Invalid Receiver ID (Will validate Indian mobile numbers only.) |
| 28683 | Invalid Date time for message Schedule (If the date specified in message post for schedule delivery is less than current date or more than expiry date or more than 1 year) |
| 28684 | Invalid SMS Block |
| 28694 | If occurred any error , related to TEMPLATEINFO parameter, which include like invalid template id is provided, variables count mismatch than the template Text variables count, template text not found for the given template id. |
| 28702 | Invalid DLT Parameters |
| 28703 | Invalid DLT Content Type |
| 28704 | Invalid Authorization Type(If message is rejected due to authorization scheme other than Authorization header) |
| Note: If message is rejected for wrong Authorization method selected then
that message is rejected on filter with Http error code 401 and description
“Unauthorized” If message is rejected for HTTPS then that message is rejected on filter with Http error code 403 and description “HTTP Not Allowed” |
|
| Status Request | |
| 8448 | Message delivered successfully |
| 8449 | Message failed |
| 8450 | Message ID is invalid |
| Scheduler Related | |
| 13568 | Command completed successfully |
| 13569 | Cannot update/delete schedule since it has already been processed |
| 13570 | Cannot update schedule since the new date-time parameter is incorrect |
| 13571 | Invalid SMS ID/GUID |
| 13572 | Invalid Status type for schedule search query. The status strings can be “PROCESSED”, “PENDING” and “ERROR” |
| 13573 | Invalid date time parameter for schedule search query |
| 13574 | Invalid GUID for GUID search query |
| 13575 | Invalid command action |
Note: There isn’t any status returned in case message is in waiting status. Therefore, there would not
be any status tag in XML in case of waiting status.
“Reason for failure” codes are SMSC specific and hence are not covered here.
