All status and error codes
With Telesign APIs you need to code against the status or error codes that come back in the content of responses, rather than using the HTTP status code.
Status codes in Telesign APIs are three- or four-digits long. Error codes are five digits long.
A transaction with an intermediate code may resolve to another status later. One with a final code will not change status in the future.
Status Codes
| Status Code | Associated text string | Description | Product |
|---|---|---|---|
| 100 | Call answered | The call was answered by the end user or voicemail. | Voice Verify |
| 101 | Not answered | No one answered the call. | Voice Verify |
| 103 | Call in progress | The call is in progress. You get back an immediate response from Telesign when you make a request, usually with this status. If you retrieve status info later, it will resolve to a different status code. | Voice Verify |
| 105 | Call not handled yet | The verification call has not yet been attempted. | Voice Verify |
| 106 | Call failed | The call did not go through. Typically this occurs when Telesign’s upstream providers fail to complete the call. Sometimes retrying will work. | Voice Verify |
| 107 | Line busy | The line was busy when the call tried to reach the end user’s device. | Voice Verify |
| 108 | Call canceled by Telesign | Call canceled by Telesign. | Voice Verify |
| 129 | Call blocked by your request | Telesign blocked the call before it was placed. This is due to your prior submitted request to blocklist this phone number. | Voice Verify |
| 130 | Call blocked by Telesign | Telesign blocks a message if it is being sent to a phone number that is on a global blocklist. | Voice Verify |
| 200 | Delivered to handset | The SMS was delivered to the end user's phone. Final | SMS, SMS Verify |
| 201 | Message is read | Message read by end user. Final | Messaging |
| 203 | Delivered to gateway | The SMS was delivered to the gateway. If the gateway responds with further information (including successful delivery to handset or delivery failure), the status is updated. Intermediate | SMS, SMS Verify |
| 207 | Error delivering SMS to handset (reason unknown) | The SMS could not be delivered to the end user's handset for an unknown reason. Final | SMS, SMS Verify |
| 210 | Temporary phone error | The SMS could not be delivered to the handset due to a temporary error with the phone. Examples - phone is turned off, not enough memory to store the message. Final | SMS, SMS Verify |
| 211 | Permanent phone error | The SMS could not be delivered to the handset due to a permanent error with the phone. For example, the phone is incompatible with SMS, or illegally registered on the network. This can happen when a phone number is blacklisted, or is incorrectly provisioned. Final | SMS, SMS Verify |
| 220 | Gateway/network cannot route message | The network cannot route the message to the handset. Final | SMS, SMS Verify |
| 221 | Message expired before delivery | The message was queued by the mobile provider and timed out before it could be delivered to the handset. Final | SMS, SMS Verify |
| 222 | SMS not supported | SMS is not supported by this phone, carrier, plan, or user. | SMS, SMS Verify |
| 229 | Message blocked by your request | This code can happen because you requested a block or because Telesign blocked on your behalf. The block is custom, meaning it applies to you and not others. | SMS Verify |
| 230 | Message blocked by Telesign | Telesign blocks a message if it is being sent to a phone number that is on a global blocklist. | SMS, SMS Verify |
| 231 | Invalid/unsupported | The content of the message is not supported. | SMS, SMS Verify |
| 233 | Message blocked due to high risk score. | It was determined that the risk score for the destination number is higher than configured maximum risk score. For that reason Telesign did not send the SMS. | SMS Verify |
| 234 | Price threshold exceeded | Message not sent due to the price exceeding your set maximum price. | |
| 237 | Message blocked in requested country | You requested that messages in a specific country be blocked, and the message was being sent to this country. | SMS, SMS Verify |
| 238 | Destination blocked by prefix | You requested that phone numbers with a particular prefix be blocked. | SMS |
| 250 | Final status unknown | The final status of the SMS cannot be determined. | SMS, SMS Verify |
| 251 | Message successfully sent out for delivery, however final confirmation of delivery to handset was not received / MO successfully sent but final confirmation of delivery to handset was not received | The message was successfully delivered to the gateway, but we cannot confirm delivery to the handset because we do not receive the final handset delivery receipts in this region. NOTE: There is a high probability that this message was successfully delivered to the handset. | SMS, SMS Verify |
| 286 | Transaction not attempted | The SMS is blocked from being sent due to the phone type not being one of the following - mobile, prepaid, personal, or pager. | SMS |
| 290 | Message in progress | The message is being sent to the SMS gateway. You get back an immediate response from Telesign when you make a request, usually with this status. If you retrieve status info later, it will resolve to a different status code. | SMS, SMS Verify |
| 291 | Queued by Telesign | Telesign is experiencing an unusually high volume and has queued the SMS message. | SMS, SMS Verify |
| 292 | Queued by gateway | The SMS gateway has queued the message. | SMS, SMS Verify |
| 295 | Status delayed | The status of the SMS is temporarily unavailable. | SMS, SMS Verify |
| 300 | Transaction successfully completed | The system was able to obtain all of the requested data for Phone ID. | Phone ID, Intelligence |
| 301 | Transaction partially completed | The system was able to obtain some of the data for Phone ID, but not all of it. | Phone ID, Intelligence |
| 500 | Transaction not attempted | No call, SMS, or Phone ID request was attempted. | All |
| 501 | Not authorized | No permissions for this resource, or authorization failed. | SMS Verify |
| 502 | Campaign error | This error can be generated if there is a problem with the short code used. | SMS, SMS Verify |
| 503 | Carrier rejected - temporary problem | This error is generated if there is an error on the carrier or operator side that is temporary and the message can be retried. | SMS, SMS Verify |
| 504 | Carrier rejected - permanent error | This error is generated if there is an error on the carrier or operator side that is permanent and the message should not be retried. | SMS, SMS Verify |
| 505 | Error on gateway - temporary error | This error is generated if there is an error on Telesign's partner side that is considered temporary and the message can be retried. | SMS, SMS Verify |
| 506 | Error on gateway - permanent error | This error is generated if there is an error on Telesign's partner side that is considered permanent and the message should not be retried. | SMS, SMS Verify |
| 507 | Invalid destination address | There is a problem with the destination address used. Either the format is not valid, or the number is not associated with any carrier, or if MSC is used it does not know about this MSISDN. | SMS, SMS Verify |
| 508 | Invalid source address | The message requires a source address. Verify that one is provided and correct. | SMS, SMS Verify |
| 509 | Parameters problem | One or more parameters used in the request is not supported. | SMS, SMS Verify |
| 510 | Message blocked by subscriber action or request | The end user has blocked receiving SMS with their carrier plan or by request or from the particular short code used. | SMS, SMS Verify |
| 511 | Subscriber low on credit | The end user exceeded their spending limits and cannot receive SMS. | SMS, SMS Verify |
| 512 | Roaming error | End user cannot receive SMS because their device that receives the messages is roaming. | SMS, SMS Verify |
| 513 | Mobile number portability error | SMS failed because ported combinations are unreachable. | SMS, SMS Verify |
| 514 | Subscriber absent | The operator/carrier is temporarily unable to reach the end user's device. | SMS, SMS Verify |
| 515 | Suspected spam | This message is considered to be spam by carrier or operator. | SMS, SMS Verify |
| 516 | Delivery channel not supported by the end user's device | The end user's device does not support the channel used for delivery. Final | SMS, Messaging |
| 517 | Selected DLT details for India not supported | The DLT template ID or entity ID in the request cannot be found by the end operator. | SMS, SMS Verify |
| 518 | Message blocked due to high risk SIM swap indicator. | The service determined that the SIM swap risk indicator for the destination number is higher than the maximum value configured for your account. For that reason Telesign did not send the SMS. | SMS Verify |
| 519 | Message not sent - requested SIM swap check could not be performed. | The service could not perform the SIM swap check. This is because either the number is out of SIM swap coverage or information about the potential SIM swap event is missing. | SMS Verify |
| 520 | Content sent is not allowed | The content in this message is not permitted by the carrier. | SMS, SMS Verify |
| 599 | Status not available | The system is unable to provide status at this time. | SMS, SMS Verify |
| 2000 | Pending | Smart Verify process attempted. | Smart Verify |
| 2028 | Failure | Blocked - the risk score after running an Intelligence check on the number is too high. | Smart Verify |
| 2800 | Request successfully completed | Phone ID (all identity attributes) | |
| 2801 | Invalid request addons parameter: {parameter_name} | Phone ID (all identity attributes) | |
| 2802 | name of add-on add-on temporarily unavailable. | Phone ID (all identity attributes) | |
| 2803 | Phone number out of name of add-on add-on coverage. | Phone ID (all identity attributes) | |
| 2804 | Phone number not applicable in name of add-on add-on. | Phone ID (all identity attributes) | |
| 2805 | No name of add-on add-on information for phone number. | Phone ID (all identity attributes) | |
| 2806 | Name of add-on add-on is not enabled. | Phone ID (all identity attributes) | |
| 2807 | Some parameters submitted in the request are not valid. | Phone ID (all identity attributes) | |
| 2808 | Invalid Request: {parameter_name} parameter is missing or empty. | Phone ID (all identity attributes) | |
| 2809 | Billing Postal Code does not match contact_plus add-on information for phone number. | Phone ID (Contact Plus add-on) | |
| 2810 | Request process failed during data collection. | Phone ID (all identity attributes) | |
| 2811 | Request processing time out. | Phone ID (all identity attributes) | |
| 2812 | name of add-on exceeded transaction hard cap. Request denied. | Phone ID (all identity attributes) | |
| 3000 | Delivered | The message was delivered to the end-user. (Final if the last channel used doesn't support Read status. Intermediate otherwise) | Messaging |
| 3001 | Message in progress | Telesign successfully received this message request and is processing it. (Intermediate) | Messaging |
| 3002 | Delivered to Gateway | The message is in the process of delivery. Once all delivery options are exhausted, the status will be updated again. (Intermediate) | Messaging |
| 3003 | Delivery error | The message could not be delivered to the end-user. (Final) | Messaging |
| 3004 | Message successfully sent out for delivery, however final confirmation of delivery to handset was not received / MO successfully sent but final confirmation of delivery to handset was not received | The message was successfully delivered to the gateway, but we cannot confirm delivery to the handset because we do not receive the final handset delivery receipts in this region. NOTE: There is a high probability that this message was successfully delivered to the handset. | Messaging |
| 3005 | Message is read | The message has been read by the end-user. (Final) | Messaging |
| 3006 | None of the channels is enabled for the customer | The channels specified in this request are all either not enabled for this customer or are invalid values. (Final) | Messaging |
| 3011 | Provider Account registration error | Messaging | |
| 3012 | Provider Account migration error | Messaging | |
| 3030 | Temporary phone error | The message could not be delivered to the handset due to a temporary error with the phone. Examples - phone is turned off, not enough memory to store the message. Final | Messaging |
| 3031 | Permanent phone error | The message could not be delivered to the handset due to a permanent error with the phone. For example, the phone is incompatible with SMS, or illegally registered on the network. This can happen when a phone number is blacklisted, or is incorrectly provisioned. Final | Messaging |
| 3032 | Gateway/network cannot route message | The network cannot route the message to the handset. Final | Messaging |
| 3033 | Message expired before delivery | The message was queued by the mobile provider and timed out before it could be delivered to the handset. Final | Messaging |
| 3034 | SMS not supported | SMS is not supported by this phone, carrier, plan, or user. | Messaging |
| 3035 | Invalid/unsupported | The content of the message is not supported. | Messaging |
| 3036 | Price threshold exceeded | Message not sent due to the price exceeding your set maximum price. | |
| 3037 | Message blocked in requested country | You requested that messages in a specific country be blocked, and the message was being sent to this country. | Messaging |
| 3038 | Destination blocked by prefix | You requested that phone numbers with a particular prefix be blocked. | Messaging |
| 3039 | Final status unknown | The final status of the SMS cannot be determined. | Messaging |
| 3040 | Queued by gateway | The SMS gateway has queued the message. | Messaging |
| 3041 | Carrier rejected - temporary problem | This error is generated if there is an error on the carrier or operator side that is temporary and the message can be retried. | Messaging |
| 3042 | Carrier rejected - permanent error | This error is generated if there is an error on the carrier or operator side that is permanent and the message should not be retried. | Messaging |
| 3043 | Error on gateway - temporary error | This error is generated if there is an error on Telesign's partner side that is considered temporary and the message can be retried. | Messaging |
| 3044 | Error on gateway - permanent error | This error is generated if there is an error on Telesign's partner side that is considered permanent and the message should not be retried. | Messaging |
| 3045 | Parameters problem | One or more parameters used in the request is not supported. | Messaging |
| 3046 | Message blocked by subscriber action or request | The end user has blocked receiving SMS with their carrier plan or by request or from the particular short code used. | Messaging |
| 3047 | Subscriber low on credit | The end user exceeded their spending limits and cannot receive SMS. | Messaging |
| 3048 | Roaming error | End user cannot receive SMS because their device that receives the messages is roaming. | Messaging |
| 3049 | Mobile number portability error | SMS failed because ported combinations are unreachable. | Messaging |
| 3050 | Subscriber absent | The operator/carrier is temporarily unable to reach the end user's device. | Messaging |
| 3051 | Suspected spam | This message is considered to be spam by carrier or operator. | Messaging |
| 3052 | Message blocked by your request | This code can happen because you requested a block or because Telesign blocked on your behalf. The block is custom, meaning it applies to you and not others. | Messaging |
| 3053 | Message blocked by Telesign | Telesign blocks a message if it is being sent to a phone number that is on a global blocklist. | Messaging |
| 3054 | Message cannot be sent to RBM provider - parsing error | Telesign’s RBM (Rich Business Messaging) partner encountered a temporary problem while sending this message. Please try again. | Messaging |
| 3055 | Delivery channel not supported by the end user's device | The end user's device does not support the channel used for delivery. Final | Messaging |
| 3056 | Message failed to deliver in specified fallback time | Delivery could not be confirmed on this channel within the fallback window; triggers the next channel (if any) to send. (Intermediate) | Messaging |
| 3057 | Invalid source address | The message requires a source address. Verify that one is provided and correct. | Messaging |
| 3058 | The requested API host is not allowed for this customer_id | Messaging | |
| 3059 | Exceeded number of elements for rich card | Messaging | |
| 3061 | Media size exceeds the limit | Messaging | |
| 3062 | MMS not supported | Messaging | |
| 3071 | Unverified phone_number requested for trial account. | Messaging | |
| 3073 | Insufficient funds in prepaid wallet | Messaging | |
| 3100 | Unknown channel specified: {channel} | This channel specified in the request is not one of the supported values; triggers the next channel (if any) to send. (Intermediate) | Messaging |
| 3101 | Invalid value for parameter phone_number: {phone_number} | Phone number is too long, too short, or contains non-digit values. (Intermediate) | Messaging |
| 3102 | Invalid value for parameter message_type: {message_type} | The value of parameter message_type is not one of the supported values: ARN, MKT, OTP. (Final) | Messaging |
| 3103 | Unsupported value for parameter external_id: {external_id} | The value of parameter external_id is longer than 100 or contains non-ASCII characters. (Final) | Messaging |
| 3104 | Invalid value for parameter account_lifecycle_event: {account_lifecycle_event} | The value of parameter account_lifecycle_event is not one of the supported values: create, sign-in, transact, update, delete. (Final) | Messaging |
| 3105 | Invalid value for parameter originating_ip: {originating_ip} | Parameter originating_ip is improperly formatted. (Final) | Messaging |
| 3106 | Invalid value for parameter callback_url: {callback_url} | The value of parameter callback_url is empty. (Final) | Messaging |
| 3107 | Invalid country code for parameter phone_number | Messaging | |
| 3108 | Invalid value for parameter message | Messaging | |
| 3109 | Invalid value for parameter sender_id | Messaging | |
| 3110 | Invalid request | The API request or its JSON payload is improperly formatted. (Final) | Messaging |
| 3112 | Specified template does not exist for selected channel | Messaging | |
| 3113 | Invalid value for parameter channel: {channels} | The value of the parameter channels contains the same channel more than once or is improperly formatted. (Final) | Messaging |
| 3114 | Specified message type not allowed outside of conversation window | Messaging | |
| 3115 | Destination phone number not in coverage | Messaging | |
| 3200 | {channel} channel is not enabled for customer | This channel is not enabled for this customer. (Intermediate) | Messaging |
| 3202 | Fallback is not enabled for Customer ID | Multiple channels are specified in the request, but fallback is not enabled for this customer. (Intermediate) | Messaging |
| 3203 | Callback URL parameter not enabled for Customer ID | Using callback_url in the API request is not allowed for this customer. (Final) | Messaging |
| 3204 | Rate limit exceeded | Allowed number of requests per second on Omnichannel API has been exceeded. (Final) | Messaging |
| 3205 | Rate Limit Exceeded | Messaging | |
| 3206 | Omnichannel Product not enabled for Customer ID | Omnichannel product is not enabled for this customer. (Final) | Messaging |
| 3207 | Messaging exceeded transaction hard cap. Request denied. | Messaging | |
| 3208 | Provider Account ID not found | Messaging | |
| 3209 | Phone number not registered for testing | Messaging | |
| 3300 | Missing parameter channels | The API request does not contain mandatory parameter channels. (Final) | Messaging |
| 3301 | Missing parameter channel | The value of the parameter channels does not contain any instances of the mandatory sub-property channel. (Final) | |
| 3302 | Missing parameter phone_number | The API request does not contain the mandatory parameter phone_number. (Final) | Messaging |
| 3303 | Missing parameter message | The API request does not contain the mandatory parameter message. (Final) | Messaging |
| 3304 | Missing parameter message_type | The API request does not contain the mandatory parameter message_type. (Final) | Messaging |
| 3305 | Missing template specific parameters | Messaging | |
| 3306 | Missing message parameters for specified channel | Message object doesn't contain required info for sending message through selected channel. (Intermediate) | Messaging |
| 3400 | Not authorized | No permissions for this resource or authorization failed. (Final) | Messaging |
| 3405 | Missing required Authorization header | Messaging | |
| 3406 | CustomerID Account Suspended | Messaging | |
| 3408 | CustomerID Account Not Found | Messaging | |
| 3409 | Invalid source IP address | Messaging | |
| 3410 | Invalid Customer ID | Messaging | |
| 3411 | Invalid API Key | Messaging | |
| 3412 | Required Authorization header is not in the correct format | Messaging | |
| 3413 | Not Allowed IP Address | Messaging | |
| 3500 | System Unavailable | The system is currently unavailable. The request should be resubmitted. (Final) | Messaging |
| 3601 | CustomerID Account Not Found | Messaging |
Error codes
| Error code | Description | Product |
|---|---|---|
| -10001 | Invalid Request: {parameter name}: {parameter value} | SMS Verify |
| -10001 | Missing Parameter: {parameter name} | SMS Verify |
| -10001 | Invalid parameter passed | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -10001 | CustomerId/RefID not found | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -10004 | Reference ID expired | Get Status |
| -10009 | Invalid source IP address | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -10033 | {phone_number} has not been verified for this trial account. | SMS Verify |
| -20001 | Invalid request | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -20002 | This product is not enabled for this CustomerID | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -20003 | This feature is not enabled for this Customer ID. | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -20,004 | This product is not enabled for this country. | SMS Verify, Voice Verify |
| -30000 | Invalid CustomerID | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30001 | Account suspended | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30002 | Account not activated | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30003 | Account limit reached | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30004 | Missing required 'Authorization' header | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30005 | Required Authorization header is not in the correct format | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30006 | Invalid signature | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30007 | Missing required 'Date' or 'x-ts-date' header | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30008 | Invalid X-TS-Auth-Method header | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30009 | Date or X-TS-Date header is not RFC822 compliant | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30010 | 'Date' or 'x-ts-date' header is not within tolerable range | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30011 | X-TS-Nonce header value is either too long or too short | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30012 | 'x-ts-nonce' header value has been used recently | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -30013 | Invalid ReferenceID for Verify Completion | Completion, Get Status |
| -30015 | Invalid API Key | SMS Verify |
| -40001 | Status unavailable | Get Status |
| -40002 | Not authorized | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -40004 | Resource not found | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -40005 | Method not allowed | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -40007 | Rate limit exceeded | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -40008 | [Product method] exceed transaction hard cap; Request denied | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -40009 | Phone number not supported | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -40023 | Number Deactivation | |
| -40025 | Message blocked by Telesign | Bulk SMS API |
| -50001 | Max retries limit reached | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50002 | Mobile 2FA registration error | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50003 | Mobile device stamp drift too large | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50051 | Invalid hashcash submitted | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50052 | Unmatched registration initiate request | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50054 | Invalid API key | Voice Verify, Number Deactivation, Smart Verify |
| -50055 | Inactive API key | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50056 | Inactive application | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50057 | Invalid verification code | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50058 | Application is not registered for push notification | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -50059 | Status not available | |
| -60001 | Phone ID Contact data not found | Phone ID |
| -60002 | Mobile 2FA registration warning | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| -90001 | System unavailable; please try again later | SMS Verify, Voice Verify, Number Deactivation, Smart Verify |
| 10000 | System unavailable, please try again later | SMS |
| 10002 | x-ts-nonce header value has been used recently | All |
| 10003 | x-ts-nonce header is either too long or too short | All |
| 10004 | Date or x-ts-date header is not within tolerable range | All |
| 10005 | Date or x-ts-date header is not RFC822 compliant | All |
| 10006 | Invalid x-ts-auth-method header | All |
| 10007 | Missing required Date or x-ts-date header | SMS |
| 10008 | Invalid signature | All |
| 10009 | Missing required Authorization header | All |
| 10009 | Invalid value for parameter message | SMS |
| 10010 | CustomerID Account Suspended | All |
| 10011 | Invalid value for parameter reference_id | All |
| 10012 | This feature is not enabled for this CustomerID | Phone ID, Intelligence, SMS |
| 10013 | Invalid Request. CustomerID Account Not Found | Phone ID, Intelligence, SMS |
| 10014 | Invalid source IP address | Phone ID, Intelligence, SMS |
| 10015 | Invalid Customer ID | Phone ID, Intelligence, SMS |
| 10017 | Customer ID / Reference ID not found | Phone ID, Intelligence, SMS |
| 10019 | Rate Limit Exceeded | Phone ID, Intelligence, SMS |
| 10020 | Messaging exceeded transaction hard cap. Request denied. | Phone ID, Intelligence, SMS |
| 10021 | The product is not enabled for this country. | SMS |
| 10022 | Invalid API Key | SMS |
| 10028 | Required Authorization header is not in the correct format | SMS |
| 10030 | Insufficient funds in prepaid wallet | All |
| 10031 | Not Allowed IP Address | SMS |
| 10032 | Request blocked due to this number appearing on a Telesign blocklist. | Phone ID, Intelligence, SMS |
| 10033 | {phone_number} has not been verified for this trial account. | SMS |
| 10033 | Unverified phone_number requested for trial account. | Intelligence, Phone ID |
| 10034 | Call with declared type blocked in country requested | SMS |
| 10035 | The requested API host is not allowed for this customer_id | SMS |
| 10036 | Reference ID expired | SMS |
| 11000 | Invalid value for parameter phone_number | Phone ID, Intelligence, SMS |
| 11001 | Invalid country code for parameter phone_number | Phone ID, Intelligence, SMS |
| 11002 | Invalid value for parameter account_id | Intelligence |
| 11003 | Invalid value for parameter account_lifecycle_event | Phone ID, Intelligence, SMS |
| 11004 | Invalid value for parameter callback_url | SMS |
| 11005 | Invalid value for parameter customer_id | Phone ID, Intelligence, SMS |
| 11006 | Invalid value for parameter device_id | Intelligence |
| 11007 | Invalid value for email_address | Intelligence |
| 11009 | Invalid value for parameter message | SMS |
| 11010 | Invalid value for parameter originating_ip | Phone ID, Intelligence, SMS |
| 11011 | Invalid value for parameter reference_id | Phone ID, Intelligence, SMS |
| 11013 | Invalid value for parameter sender_id | SMS |
| 11016 | Invalid value for parameter external_id | SMS |
| 11017 | Invalid value for parameter device_id | SMS |
| 11024 | Invalid value for parameter phone_number_1 | SMS |
| 11025 | Invalid value for parameter phone_number_2 | SMS |
| 11034 | Invalid value for parameter dlt_template_id | SMS |
| 11035 | Invalid value for parameter dlt_entity_id | SMS |
| 12000 | Missing required parameter phone_number | Phone ID, Intelligence, SMS |
| 12003 | Missing required parameter account_lifecycle_event | Intelligence |
| 12009 | Missing required parameter message | SMS |
| 12017 | Missing required parameter message_type | SMS |
Updated about 1 month ago