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 API |
| 101 | Not answered | No one answered the call. | Voice Verify API |
| 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 API |
| 105 | Call not handled yet | The verification call has not yet been attempted. | Voice Verify API |
| 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 API |
| 107 | Line busy | The line was busy when the call tried to reach the end user’s device. | Voice Verify API |
| 108 | Call canceled by Telesign | Call canceled by Telesign. | Voice Verify API |
| 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 API |
| 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 API |
| 200 | Delivered to handset | The SMS was delivered to the end user's phone. Final | SMS, SMS Verify API |
| 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 API |
| 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 API |
| 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 API |
| 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 API |
| 220 | Gateway/network cannot route message | The network cannot route the message to the handset. Final | SMS, SMS Verify API |
| 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 API |
| 222 | SMS not supported | SMS is not supported by this phone, carrier, plan, or user. | SMS, SMS Verify API |
| 229 | Message blocked by customer 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 API |
| 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 Verify API |
| 231 | Invalid/unsupported | Invalid/unsupported message content | SMS, SMS Verify API |
| 233 | Message blocked due to high risk score. | You requested that messages in a specific country be blocked, and the message was being sent to this country | SMS Verify API |
| 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 API |
| 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 API |
| 251 | Message successfully sent out for delivery, however final confirmation of delivery to handset was not received. | Telesign successfully delivered the message through our gateway and it passed downstream. However, Telesign did not receive a delivery receipt within 12 hours of transmission. We cannot confirm delivery to the handset. The end user most likely did not receive the message. | SMS, SMS Verify API |
| 251 | Message successfully sent out for delivery, however final confirmation of delivery to handset was not received. | Message successfully sent out for delivery, however final confirmation of delivery to handset was not received. | Bulk 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 API |
| 292 | Queued by gateway | The SMS gateway has queued the message. | SMS, SMS Verify API |
| 293 | Bulk request accepted | The bulk request was accepted by Telesign. | Bulk SMS |
| 295 | Status delayed | The status of the SMS is temporarily unavailable. | SMS, SMS Verify API |
| 300 | Transaction successfully completed | The system was able to obtain all of the requested data for Intelligence or Phone ID. | Phone ID, Intelligence |
| 301 | Transaction partially completed | The system was able to obtain some of the data for Intelligence or Phone ID, but not all of it. | Phone ID, Intelligence |
| 500 | Transaction not attempted | No call, message send, or other processing of the request was attempted. | All (Excluding SMS Verify API) |
| 501 | Not authorized | No permissions for this resource, or authorization failed. | SMS Verify API, SMS |
| 502 | Campaign error | This error can be generated if there is a problem with the short code used. | SMS, SMS Verify API |
| 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 API |
| 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 API |
| 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 API |
| 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 API |
| 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 API |
| 508 | Invalid source address | The message requires a source address. Verify that one is provided and correct. | SMS, SMS Verify API |
| 509 | Parameters problem | One or more parameters used in the request is not supported. | SMS, SMS Verify API |
| 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 API |
| 511 | Subscriber low on credit | The end user exceeded their spending limits and cannot receive SMS. | SMS, SMS Verify API |
| 512 | Roaming error | End user cannot receive SMS because their device that receives the messages is roaming. | SMS, SMS Verify API |
| 513 | Mobile number portability error | SMS failed because ported combinations are unreachable. | SMS, SMS Verify API |
| 514 | Subscriber absent | The operator/carrier is temporarily unable to reach the end user's device. | SMS, SMS Verify API |
| 515 | Suspected spam | This message is considered to be spam by carrier or operator. | SMS, SMS Verify API |
| 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 | 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 API |
| 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 API |
| 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 API |
| 520 | Content sent is not allowed | The content in this message is not permitted by the carrier. | SMS, SMS Verify API |
| 521 | Requested Sender ID is not allowed for destination | The sender ID submitted in request is not allowed in destination country/operator. | SMS Verify API |
| 521 | Requested Sender ID is not allowed for destination | The sender ID submitted in request is not allowed in destination country/operator. | SMS |
| 599 | Status not available | The system is unable to provide status at this time. | SMS, SMS Verify API |
| 1900 | Verify completion successfully recorded | The confirmation that the end-user has received the message has been successfully recorded. | Get Status |
| 2000 | Pending | Smart Verify API process attempted. | Smart Verify API |
| 2028 | Failure | Blocked - the risk recommendation after running an Intelligence check on the number is too high. | Smart Verify API |
| 2800 | Request successfully completed | The request was successfully processed with valid parameters. | Phone ID (all identity attributes) |
| 2801 | Invalid request addons parameter: {parameter_name} | The specified parameter_name is not a valid parameter for this request and cannot be processed. Remove or replace it with a valid parameter. | Phone ID (all identity attributes) |
| 2802 | name of add-on add-on temporarily unavailable. | The requested add-on is currently unavailable and cannot be accessed at this time. | Phone ID (all identity attributes) |
| 2803 | Phone number out of name of add-on add-on coverage. | The specified phone number is not supported for the requested add-on service. | Phone ID (all identity attributes) |
| 2804 | Phone number not applicable in name of add-on add-on. | The provided phone number is not applicable for use with the requested add-on. | Phone ID (all identity attributes) |
| 2805 | No name of add-on add-on information for phone number. | No information could be retrieved for the provided phone number for the requested add-on. | Phone ID (all identity attributes) |
| 2806 | Name of add-on add-on is not enabled. | The requested add-on is not enabled for your account. | Phone ID (all identity attributes) |
| 2807 | Some parameters submitted in the request are not valid. | One or more parameters in the request are incorrect or do not conform to the expected format. | Phone ID (all identity attributes) |
| 2808 | Invalid Request: {parameter_name} parameter is missing or empty. | The required parameter parameter_name is missing or has no value. | Phone ID (all identity attributes) |
| 2809 | Billing Postal Code does not match contact_plus add-on information for phone number. | The Billing Postal Code provided does not match the information associated with the phone number in the contact_plus add-on. | Phone ID (Contact Plus add-on) |
| 2810 | Request process failed during data collection. | The request could not be completed due to an issue during the data collection phase. | Phone ID (all identity attributes) |
| 2811 | Request processing time out. | The request could not be processed within the allotted time and has timed out. | Phone ID (all identity attributes) |
| 2812 | name of add-on exceeded transaction hard cap. Request denied. | The transaction limit for the add-on has been exceeded, and the request was 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 | 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. | Messaging |
| 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 CustomerID | The requested API host is not allowed for the account associated with this customer ID. | Messaging |
| 3059 | Exceeded number of elements for rich card | The number of elements (e.g., buttons, images) added exceeds the allowed number of elements for a rich card. | Messaging |
| 3060 | Delivery channel supported by the end user's device | The device associated with this phone number can use the selected channel. | Messaging |
| 3061 | Media size exceeds the limit | The media file size exceeds the maximum allowed limit and cannot be sent. | Messaging |
| 3062 | MMS not supported | MMS is not supported for this request and could not be processed. | Messaging |
| 3071 | Unverified phone_number requested for trial account. | The phone number must be verified before it can be used in requests on a trial account. | Messaging |
| 3072 | 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 message. | Messaging |
| 3073 | Insufficient funds in prepaid wallet | The prepaid wallet balance is insufficient to complete the requested transaction. | 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 value for parameter country_code | The provided country code is either in an incorrect format or not one of the expected values. | Messaging |
| 3108 | Invalid value for parameter message | The message parameter has an invalid format or contains unexpected content. | Messaging |
| 3109 | Invalid value for parameter sender_id: {sender_id} | The specified sender ID does not match the expected value or is in an incorrect format. Ensure the provided sender ID has been created and is valid for your account. | 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 | The template specified in the request does not exist for the selected messaging 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 | The specified message type is not allowed to be sent outside of a conversation window. | Messaging |
| 3115 | Destination phone number not in coverage | The number you are trying to send a message to is not within the coverage area for message delivery. | 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 | Allowed number of SMS transactions per second has been exceeded. | Messaging |
| 3206 | Omnichannel Product not enabled for Customer ID | Omnichannel product is not enabled for this customer. (Final) | Messaging |
| 3207 | Product exceeded transaction hard cap. Request denied. | Product exceeded transaction hard cap limit. Request denied. | Messaging |
| 3208 | Provider Account ID not found | The Provider Account ID could not be found in the system. | Messaging |
| 3209 | End-user not registered for testing | The end user's phone number has not been registered for use in testing requests. | 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) | Messaging |
| 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 | The request is missing one or more required parameters specific to the selected template. | 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 | The request is missing the required Authorization header for authentication. | Messaging |
| 3406 | CustomerID Account Suspended. | The account associated with the provided Customer ID has been suspended. | Messaging |
| 3408 | CustomerID Account Not Found | The account associated with the provided Customer ID could not be found in the system. | Messaging |
| 3409 | Invalid source IP address. | The source IP address provided is not recognized or is invalid. | Messaging |
| 3410 | Invalid Customer ID. | The provided Customer ID is invalid or does not exist in the system. | Messaging |
| 3411 | Invalid API Key. | The API key provided is invalid or does not match the expected format. | Messaging |
| 3412 | Required 'Authorization' header is not in the correct format | The Authorization header is not in the correct format and cannot be processed. | Messaging |
| 3413 | Not Allowed Host | The host is not authorized to access the system. | Messaging |
| 3500 | System Unavailable | The system is currently unavailable. The request should be resubmitted. (Final) | Messaging |
| 3601 | Missing providers tracking data | The required tracking data from the provider is missing. | Messaging |
| 4501 | Success | Verification flow started in Silent Verify Initiate. | Silent Verify API |
| 4501 | Successfully verified | Device successfully verified on Silent Verify Finalize. | Silent Verify API |
| 4502 | The phone number does not match | Unable to verify the device because the phone number isn't associated with the device. | Silent Verify API |
| 5000 | New key was successfully created. | A new REST API key was successfully created for your account. | Accounts API |
| 5001 | Key list was successfully retrieved. | A list of REST API key objects associated with your account was successfully returned. | Accounts API |
| 5002 | Key object was successfully retrieved. | The specified REST API key object associated with your account was successfully returned. | Accounts API |
| 5003 | Key was successfully updated. | The specified REST API key has been successfully updated and the key object with its new details has been returned. | Accounts API |
| 5004 | Key successfully expired. | The specified REST API key has been successfully expired and removed from the list of active keys for your account. | Accounts API |
| 5005 | New account was successfully created. | You have successfully cloned your account and created a new one. | Accounts API |
| 5101 | Invalid value for body parameter {param name} | The provided value for the body parameter param name is invalid or does not match the expected format. | Accounts API |
| 5103 | Invalid value for path parameter {param name} | The provided value for the path parameter param name is invalid or does not match the expected format. | Accounts API |
| 5110 | Request payload is improperly formatted. | The request payload is not properly structured or contains invalid data. Ensure that all required parameters are included and correct, and that the request format is valid. | Accounts API |
| 5111 | The limit of {max_no_keys} keys has been reached. | The maximum limit of keys has been reached and no additional keys can be added. | Accounts API |
| 5112 | Missing required parameter {param_name}. | The required parameter param_name is missing from the request and must be provided. | Accounts API |
| 5113 | {date-time-stamp} is not a valid future date. | The provided date-time stamp does not represent a future date or is invalid. | Accounts API |
| 5114 | Too many users included in the request. | The request includes more users than the allowed limit and cannot be processed. | Accounts API |
| 5204 | Rate limit exceeded. | Allowed number of requests per second on Accounts API has been exceeded. | Accounts API |
| 5400 | Authentication failed. | Authentication failed due to invalid credentials or missing required authentication details. | Accounts API |
| 5401 | No permissions for this resource. | The account does not have the necessary permissions to access the requested resource. | Accounts API |
| 5500 | System unavailable. Please try again later. | The system is currently unavailable. The request should be resubmitted. | Accounts API |
| 10000 | System Unavailable, Please try again later. | The system is currently unavailable. The request should be resubmitted. | SMS |
| 10002 | 'x-ts-nonce' header value has been used recently | The x-ts-nonce header value cannot be reused in this request because it was used recently. | SMS |
| 10003 | 'x-ts-nonce' header value is either too long or too short | The x-ts-nonce header value is either too long or too short. Ensure that x-ts-nonce is within the acceptable length. | SMS |
| 10004 | 'Date' or 'x-ts-date' header is not within tolerable range | The Date or x-ts-date header value is outside the acceptable range. Ensure that it is within the acceptable range. | SMS |
| 10005 | 'Date' or 'x-ts-date' header is not RFC822 compliant | The Date or x-ts-date header value is not RFC822 compliant and cannot be processed. | SMS |
| 10006 | Invalid 'x-ts-auth-method' header. | The x-ts-auth-method header value is invalid and cannot be processed. | SMS |
| 10007 | Missing required 'Date' or 'x-ts-date' header | The required Date or x-ts-date header is missing and must be included in the request. | SMS |
| 10008 | Invalid Signature. | The signature provided is invalid and cannot be verified. | SMS |
| 10009 | Missing required Authorization header | The request is missing the required Authorization header for authentication. | SMS |
| 10010 | CustomerID Account Suspended | The account associated with the provided Customer ID has been suspended. | SMS |
| 10011 | This product is not enabled for this CustomerID. | SMS product is not enabled for this customer. | SMS |
| 10014 | Invalid source IP address. | The source IP address provided is not recognized or is invalid. | SMS |
| 10015 | Invalid Customer ID. | The provided Customer ID is invalid or does not exist in the system. | SMS |
| 10019 | Rate Limit Exceeded | Allowed number of requests per second on SMS has been exceeded. | SMS |
| 10020 | Generic messaging exceeded transaction hard cap. Request denied. | The transaction limit for generic messaging has been exceeded, and the request was denied. | SMS |
| 10022 | Invalid API Key. | The API key provided is invalid or does not match the expected format. | SMS |
| 10028 | Required 'Authorization' header is not in the correct format | The Authorization header is not in the correct format and cannot be processed. | SMS |
| 10030 | Insufficient funds in prepaid wallet. | The prepaid wallet balance is insufficient to complete the requested transaction. | SMS |
| 10031 | Not Allowed Host | The host is not authorized to access the system. | SMS |
| 10031 | Message blocked by customer 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 (DLR Callback only) |
| 10032 | Message blocked by TeleSign | Telesign blocks a message if it is being sent to a phone number that is on a global blocklist. | SMS |
| 10033 | {phone_number} has not been verified for this trial account. | The phone number must be verified before it can be used in requests on a trial account. | SMS |
| 10035 | The requested API host is not allowed for this CustomerID. | The requested API host is not allowed for the account associated with this customer ID. | SMS |
| 10036 | Reference ID expired | The provided reference ID has expired and is no longer valid. | SMS |
| 11000 | Invalid value for parameter phone_number. | Phone number is too long, too short, or contains non-digit values. | SMS |
| 11001 | Invalid country code for parameter phone_number. | The provided country code is either in an incorrect format or not one of the expected values. | SMS |
| 11003 | Invalid value for parameter account_lifecycle_event | The value of parameter account_lifecycle_event is not one of the supported values: create, sign-in, transact, update, delete. | SMS |
| 11004 | Invalid value for parameter callback_url | The value of parameter callback_url is empty. | SMS |
| 11009 | Invalid value for parameter message. | The message parameter has an invalid format or contains unexpected content. | SMS |
| 11010 | Invalid value for parameter originating_ip. | Parameter originating_ip is improperly formatted. | SMS |
| 11011 | Invalid value for parameter reference_id | The provided value for the reference_id parameter is invalid or does not match the expected format. | SMS |
| 11013 | Invalid value for parameter sender_id. | The specified sender ID does not match the expected value or is in an incorrect format. Ensure the provided sender ID has been created and is valid for your account. | SMS |
| 11016 | Invalid value for parameter external_id | The value of parameter external_id is longer than 100 or contains non-ASCII characters. | SMS |
| 11017 | Invalid value for parameter message_type. | The value of parameter message_type is not one of the supported values: ARN, MKT, OTP. | SMS |
| 11027 | Invalid value for parameter integration_name. | The provided value for the integration_name parameter is invalid or does not match the expected format. | SMS |
| 11034 | Invalid value for parameter dlt_template_id | The provided value for the dlt_template_id parameter is invalid or does not match the expected format. | SMS |
| 11035 | Invalid value for parameter dlt_entity_id | The provided value for the dlt_entity_id parameter is invalid or does not match the expected format. | SMS |
| 12000 | Missing Required Parameter phone_number | The required parameter phone_number is missing from the request and must be provided. | SMS |
| 12009 | Missing Required Parameter message | The required parameter message is missing from the request and must be provided. | SMS |
| 12017 | Missing Required Parameter message_type | The required parameter message_type is missing from the request and must be provided. | SMS |
| -10001 | Invalid parameter passed | The parameter provided in the request is invalid or does not meet the required format. | Completion |
| -10001 | Customer ID / Reference ID not found | The Customer ID or the Reference ID could not be found in the system. | Completion |
| -30000 | Invalid customer ID | The provided Customer ID is invalid or does not exist in the system. | Completion |
| -30001 | Account suspended | The account has been suspended. | Completion |
| -30002 | Account not activated | The account has not been activated and cannot be used. | Completion |
| -30003 | Account limit reached | The account has reached its limit and can no longer process additional requests. | Completion |
| -30004 | Missing required Authorization header | The request is missing the required Authorization header for authentication. | Completion |
| -30005 | Required Authorization header is not in the correct format | The Authorization header is not in the correct format and cannot be processed. | Completion |
| -30006 | Invalid signature | The signature provided is invalid and cannot be verified. | Completion |
| -30007 | Missing required Date or X-TS-Date header | The required Date or x-ts-date header is missing and must be included in the request. | Completion |
| -30008 | Invalid X-TS-Auth-Method header | The x-ts-auth-method header value is invalid and cannot be processed. | Completion |
| -30009 | Date or X-TS-Date header is not RFC822 compliant | The Date or x-ts-date header value is not RFC822 compliant and cannot be processed. | Completion |
| -30010 | Date or X-TS-Date header is not within tolerable range | The Date or x-ts-date header value is outside the acceptable range. Ensure that it is within the acceptable range. | Completion |
| -30011 | X-TS-Nonce header value is either too long or too short | The x-ts-nonce header value is either too long or too short. Ensure that x-ts-nonce is within the acceptable length. | Completion |
| -30012 | X-TS-Nonce header value has been used recently | The x-ts-nonce header value cannot be reused in this request because it was used recently. | Completion |
| -30013 | Invalid ReferenceID for Verify Completion | The provided Reference ID is invalid or does not exist in the system. | Completion |
Error codes
| Error code | Description | Product |
|---|---|---|
| -10001 | Invalid Request: ReferenceID Parameter: <reference_id> | SMS Verify API |
| -10001 | Invalid Request: CustomerID Parameter: <customer_id> | SMS Verify API |
| -10001 | Invalid Request: AuthenticationID | SMS Verify API |
| -10001 | Invalid Request: CustomerID/AuthenticationID Parameter: <customer_id>/<authentication_id> | SMS Verify API |
| -10001 | Invalid Request: customer_id Parameter: <customer_id> | SMS Verify API |
| -10001 | Not Allowed Host | SMS Verify API, Voice Verify API |
| -10001 | CustomerID/ReferenceID not found Parameter: CustomerID/ReferenceID: <customer_id>/<reference_id> | SMS Verify API |
| -10001 | CustomerID/ReferenceID not found | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -10001 | Invalid parameter passed | Voice Verify API, Number Deactivation, Smart Verify API |
| -10001 | Invalid Request: Missing parameter Parameter: Template | Bulk SMS |
| -10002 | Empty recipients list | Bulk SMS |
| -10003 | Max number of recipients exceeded | Bulk SMS |
| -10004 | Reference ID expired | Get Status |
| -10009 | Invalid source IP address | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API, Bulk SMS |
| -10030 | Insufficient funds in prepaid wallet. | SMS Verify |
| -10033 | {phone_number} has not been verified for this trial account. | SMS Verify API |
| -20001 | Invalid request | Voice Verify API, Number Deactivation, Smart Verify API |
| -20001 | Invalid Request: CustomerID Parameter: <customer_id> | SMS Verify API |
| -20002 | This product is not enabled for this CustomerID | Voice Verify API, Number Deactivation, Smart Verify API |
| -20002 | This product is not enabled for this Customer ID. | SMS Verify API, Bulk SMS |
| -20003 | This feature is not enabled for this Customer ID. | Voice Verify API, Number Deactivation, Smart Verify API |
| -20004 | This product is not enabled for this country. | Voice Verify API |
| -30000 | Invalid CustomerID | Voice Verify API, Number Deactivation, Smart Verify API |
| -30000 | Invalid Customer ID | SMS Verify API, Bulk SMS |
| -30001 | Account suspended | Voice Verify API, Number Deactivation, Smart Verify API |
| -30001 | Customer ID Account Suspended. | SMS Verify API, Bulk SMS |
| -30002 | Account not activated | Voice Verify API, Number Deactivation, Smart Verify API |
| -30002 | Customer ID Account Not Activated. | SMS Verify API |
| -30003 | Account limit reached | Voice Verify API, Number Deactivation, Smart Verify API |
| -30003 | Customer ID new account limit reached. | SMS Verify API |
| -30004 | Missing required 'Authorization' header | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -30005 | Required Authorization header is not in the correct format | Voice Verify API, Number Deactivation, Smart Verify API |
| -30005 | Required 'Authorization' header is not in the correct format | SMS Verify API |
| -30006 | Invalid signature | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -30007 | Missing required 'Date' or 'x-ts-date' header | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -30008 | Invalid X-TS-Auth-Method header | Voice Verify API, Number Deactivation, Smart Verify API |
| -30008 | Invalid 'x-ts-auth-method' header. | SMS Verify API |
| -30009 | Date or X-TS-Date header is not RFC822 compliant | Voice Verify API, Number Deactivation, Smart Verify API |
| -30009 | 'Date' or 'x-ts-date' header is not RFC822 compliant | SMS Verify API |
| -30010 | 'Date' or 'x-ts-date' header is not within tolerable range | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -30011 | X-TS-Nonce header value is either too long or too short | Voice Verify API, Number Deactivation, Smart Verify API |
| -30011 | 'x-ts-nonce' header value is either too long or too short | SMS Verify API |
| -30012 | 'x-ts-nonce' header value has been used recently | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -30013 | Invalid ReferenceID for Verify Completion | Completion, Get Status |
| -30015 | Invalid API Key | SMS Verify API |
| -40001 | Status unavailable | Get Status |
| -40002 | Not authorized | Voice Verify API, Number Deactivation, Smart Verify API |
| -40004 | Resource not found | Voice Verify API, Number Deactivation, Smart Verify API |
| -40005 | Method not allowed | Voice Verify API, Number Deactivation, Smart Verify API |
| -40006 | Bad Request | Bulk SMS |
| -40007 | Rate limit exceeded | Voice Verify API, Number Deactivation, Smart Verify API, SMS Verify API |
| -40007 | Rate Limit Exceeded | SMS Verify API, Bulk SMS |
| -40008 | [Product method] exceed transaction hard cap; Request denied | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -40008 | Verify SMS exceeded transaction hard cap. Request denied. | Bulk SMS |
| -40009 | Phone number not supported | SMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API |
| -40023 | Number Deactivation | |
| -40024 | Message blocked by customer request | Bulk SMS |
| -40025 | Message blocked by Telesign | Bulk SMS |
| -50001 | Max retries limit reached | Voice Verify API, Number Deactivation, Smart Verify API |
| -50002 | Mobile 2FA registration error | Voice Verify API, Number Deactivation, Smart Verify API |
| -50003 | Mobile device stamp drift too large | Voice Verify API, Number Deactivation, Smart Verify API |
| -50051 | Invalid hashcash submitted | Voice Verify API, Number Deactivation, Smart Verify API |
| -50052 | Unmatched registration initiate request | Voice Verify API, Number Deactivation, Smart Verify API |
| -50054 | Invalid API key | Voice Verify API, Number Deactivation, Smart Verify API |
| -50055 | Inactive API key | Voice Verify API, Number Deactivation, Smart Verify API |
| -50056 | Inactive application | Voice Verify API, Number Deactivation, Smart Verify API |
| -50057 | Invalid verification code | Voice Verify API, Number Deactivation, Smart Verify API |
| -50058 | Application is not registered for push notification | Voice Verify API, Number Deactivation, Smart Verify API |
| -50059 | Status not available | |
| -60001 | Phone ID Contact data not found | Phone ID |
| -60002 | Mobile 2FA registration warning | Voice Verify API, Number Deactivation, Smart Verify API |
| -90001 | System unavailable; please try again later | Voice Verify API, Number Deactivation, Smart Verify API |
| -90001 | System Unavailable, please try again later. | SMS Verify API, Bulk SMS |
| 10000 | System unavailable, please try again later. | Silent Verify API |
| 10004 | Bad request | Silent Verify API |
| 10008 | Invalid signature | Phone ID, Intelligence |
| 10009 | Invalid value for parameter message | Phone ID, Intelligence |
| 10010 | CustomerID Account Suspended | Phone ID, Intelligence |
| 10011 | Invalid value for parameter reference_id | Silent Verify API |
| 10012 | This feature is not enabled for this CustomerID | Phone ID, Intelligence |
| 10013 | Invalid Request. CustomerID Account Not Found | Phone ID, Intelligence |
| 10014 | Invalid source IP address | Phone ID, Intelligence |
| 10015 | Invalid Customer ID | Phone ID, Intelligence |
| 10017 | Customer ID / Reference ID not found | Phone ID, Intelligence |
| 10019 | Rate Limit Exceeded | Phone ID, Intelligence, Silent Verify |
| 10020 | Messaging exceeded transaction hard cap. Request denied. | Phone ID, Intelligence |
| 10032 | Request blocked due to this number appearing on a Telesign blocklist. | Phone ID, Intelligence |
| 10033 | Unverified phone_number requested for trial account. | Intelligence, Phone ID |
| 10039 | Internal server error | Silent Verify API |
| 11000 | Invalid value for parameter phone_number | Phone ID, Intelligence, Silent Verify API |
| 11001 | Invalid country code for parameter phone_number | Phone ID, Intelligence |
| 11002 | Invalid value for parameter account_id | Intelligence |
| 11003 | Invalid value for parameter account_lifecycle_event | Phone ID, Intelligence |
| 11005 | Invalid value for parameter customer_id | Phone ID, Intelligence |
| 11006 | Invalid value for parameter device_id | Intelligence |
| 11007 | Invalid value for email_address | Intelligence |
| 11010 | Invalid value for parameter originating_ip | Phone ID, Intelligence |
| 11011 | Invalid value for parameter reference_id | Phone ID, Intelligence |
| 11024 | Invalid value for parameter phone_number_1 | Number Masking |
| 11025 | Invalid value for parameter phone_number_2 | Number Masking |
| 12000 | Missing required parameter phone_number | Phone ID, Intelligence |
| 12003 | Missing required parameter account_lifecycle_event | Intelligence |
| 40001 | Request timeout | Silent Verify API |
| 40002 | Not authorized | Silent Verify API |
| 40003 | No end client data found on records | Silent Verify API |
| 40004 | The required parameter 'verification' is missing from the request | Silent Verify API |
| 40010 | Not in coverage. The phone number being verified is not within the provider's network. | Silent Verify API |
| 45005 | Error on gateway - temporary error. This error is generated if there is an error on Telesign's partner side that is considered temporary. You can try to send the message again. | Silent Verify API |
| 45006 | Error on gateway - permanent error. This error is generated if there is an error on Telesign's partner side that is considered permanent. You should not try to send the message again. | Silent Verify API |
| 45010 | Provider not available to route the request. This error can occur when providers not are available in the geographical area to route the request or when all providers failed (with errors) to complete the requests. | Silent Verify API |
Updated 3 months ago