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 CodeAssociated text stringDescriptionProduct
100Call answeredThe call was answered by the end user or voicemail.Voice Verify API
101Not answeredNo one answered the call.Voice Verify API
103Call in progressThe 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
105Call not handled yetThe verification call has not yet been attempted.Voice Verify API
106Call failedThe 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
107Line busyThe line was busy when the call tried to reach the end user’s device.Voice Verify API
108Call canceled by TelesignCall canceled by Telesign.Voice Verify API
129Call blocked by your requestTelesign blocked the call before it was placed. This is due to your prior submitted request to blocklist this phone number.Voice Verify API
130Call blocked by TelesignTelesign blocks a message if it is being sent to a phone number that is on a global blocklist.Voice Verify API
200Delivered to handsetThe SMS was delivered to the end user's phone. FinalSMS, SMS Verify API
201Message is readMessage read by end user. FinalMessaging
203Delivered to gatewayThe 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. IntermediateSMS, SMS Verify API
207Error delivering SMS to handset (reason unknown)The SMS could not be delivered to the end user's handset for an unknown reason. FinalSMS, SMS Verify API
210Temporary phone errorThe 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. FinalSMS, SMS Verify API
211Permanent phone errorThe 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. FinalSMS, SMS Verify API
220Gateway/network cannot route messageThe network cannot route the message to the handset. FinalSMS, SMS Verify API
221Message expired before deliveryThe message was queued by the mobile provider and timed out before it could be delivered to the handset. FinalSMS, SMS Verify API
222SMS not supportedSMS is not supported by this phone, carrier, plan, or user.SMS, SMS Verify API
229Message blocked by customer requestThis 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, SMS
230Message blocked by TelesignTelesign blocks a message if it is being sent to a phone number that is on a global blocklist.SMS, SMS Verify API
231Invalid/unsupportedInvalid/unsupported message contentSMS, SMS Verify API
233Message blocked due to high risk score.You requested that messages in a specific country be blocked, and the message was being sent to this countrySMS Verify API
234Price threshold exceededMessage not sent due to the price exceeding your set maximum price.
237Message blocked in requested countryYou requested that messages in a specific country be blocked, and the message was being sent to this country.SMS, SMS Verify API
238Destination blocked by prefixYou requested that phone numbers with a particular prefix be blocked.SMS, SMS Verify API
250Final status unknownThe final status of the SMS cannot be determined.SMS, SMS Verify API
251Message 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 receivedThe 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 Verify API
251Message successfully sent out for delivery, however final confirmation of delivery to handset was not received.This message was successfully delivered to the gateway, but Telesign cannot confirm delivery to the handset because Telesign does not receive the final handset DLR in this region. NOTE: There is a high probability that this message was successfully delivered to the handset.SMS
286Transaction not attemptedThe SMS is blocked from being sent due to the phone type not being one of the following - mobile, prepaid, personal, or pager.SMS, SMS Verify API
290Message in progressThe 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
291Queued by TelesignTelesign is experiencing an unusually high volume and has queued the SMS message.SMS, SMS Verify API
292Queued by gatewayThe SMS gateway has queued the message.SMS, SMS Verify API
293Bulk request acceptedThe bulk request was accepted by Telesign.Bulk SMS
295Status delayedThe status of the SMS is temporarily unavailable.SMS, SMS Verify API
300Transaction successfully completedThe system was able to obtain all of the requested data for Intelligence or Phone ID.Phone ID, Intelligence
301Transaction partially completedThe system was able to obtain some of the data for Intelligence or Phone ID, but not all of it.Phone ID, Intelligence
500Transaction not attemptedNo call, message send, or other processing of the request was attempted.All (Excluding SMS Verify API)
501Not authorizedNo permissions for this resource, or authorization failed.SMS Verify API, SMS
502Campaign errorThis error can be generated if there is a problem with the short code used.SMS, SMS Verify API
503Carrier rejected - temporary problemThis 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
504Carrier rejected - permanent errorThis 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
505Error on gateway - temporary errorThis 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
506Error on gateway - permanent errorThis 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
507Invalid destination addressThere 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
508Invalid source addressThe message requires a source address. Verify that one is provided and correct.SMS, SMS Verify API
509Parameters problemOne or more parameters used in the request is not supported.SMS, SMS Verify API
510Message blocked by subscriber action or requestThe end user has blocked receiving SMS with their carrier plan or by request or from the particular short code used.SMS, SMS Verify API
511Subscriber low on creditThe end user exceeded their spending limits and cannot receive SMS.SMS, SMS Verify API
512Roaming errorEnd user cannot receive SMS because their device that receives the messages is roaming.SMS, SMS Verify API
513Mobile number portability errorSMS failed because ported combinations are unreachable.SMS, SMS Verify API
514Subscriber absentThe operator/carrier is temporarily unable to reach the end user's device.SMS, SMS Verify API
515Suspected spamThis message is considered to be spam by carrier or operator.SMS, SMS Verify API
516Delivery channel not supported by the end user's deviceThe end user's device does not support the channel used for delivery. FinalSMS, Messaging
517Selected DLT details for India not supportedThe DLT template ID or entity ID in the request cannot be found by the end operator.SMS, SMS Verify API
518Message 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
519Message 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
520Content sent is not allowedThe content in this message is not permitted by the carrier.SMS, SMS Verify API
521Requested Sender ID is not allowed for destinationThe sender ID submitted in request is not allowed in destination country/operator.SMS Verify API
521Requested Sender ID is not allowed for destinationThe sender ID submitted in request is not allowed in destination country/operator.SMS
599Status not availableThe system is unable to provide status at this time.SMS, SMS Verify API
2000PendingSmart Verify API process attempted.Smart Verify API
2028FailureBlocked - the risk score after running an Intelligence check on the number is too high.Smart Verify API
2800Request successfully completedPhone ID (all identity attributes)
2801Invalid request addons parameter: {parameter_name}Phone ID (all identity attributes)
2802name of add-on add-on temporarily unavailable.Phone ID (all identity attributes)
2803Phone number out of name of add-on add-on coverage.Phone ID (all identity attributes)
2804Phone number not applicable in name of add-on add-on.Phone ID (all identity attributes)
2805No name of add-on add-on information for phone number.Phone ID (all identity attributes)
2806Name of add-on add-on is not enabled.Phone ID (all identity attributes)
2807Some parameters submitted in the request are not valid.Phone ID (all identity attributes)
2808Invalid Request: {parameter_name} parameter is missing or empty.Phone ID (all identity attributes)
2809Billing Postal Code does not match contact_plus add-on information for phone number.Phone ID (Contact Plus add-on)
2810Request process failed during data collection.Phone ID (all identity attributes)
2811Request processing time out.Phone ID (all identity attributes)
2812name of add-on exceeded transaction hard cap. Request denied.Phone ID (all identity attributes)
3000DeliveredThe message was delivered to the end-user. (Final if the last channel used doesn't support Read status. Intermediate otherwise)Messaging
3001Message in progressTelesign successfully received this message request and is processing it. (Intermediate)Messaging
3002Delivered to GatewayThe message is in the process of delivery. Once all delivery options are exhausted, the status will be updated again. (Intermediate)Messaging
3003Delivery errorThe message could not be delivered to the end-user. (Final)Messaging
3004Message 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 receivedThe 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
3005Message is readThe message has been read by the end-user. (Final)Messaging
3006None of the channels is enabled for the customerThe channels specified in this request are all either not enabled for this customer or are invalid values. (Final)Messaging
3011Provider Account registration errorMessaging
3012Provider Account migration errorMessaging
3030Temporary phone errorThe 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. FinalMessaging
3031Permanent phone errorThe 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. FinalMessaging
3032Gateway/network cannot route messageThe network cannot route the message to the handset. FinalMessaging
3033Message expired before deliveryThe message was queued by the mobile provider and timed out before it could be delivered to the handset. FinalMessaging
3034SMS not supportedSMS is not supported by this phone, carrier, plan, or user.Messaging
3035Invalid/unsupportedThe content of the message is not supported.Messaging
3036Price threshold exceededMessage not sent due to the price exceeding your set maximum price.
3037Message blocked in requested countryYou requested that messages in a specific country be blocked, and the message was being sent to this country.Messaging
3038Destination blocked by prefixYou requested that phone numbers with a particular prefix be blocked.Messaging
3039Final status unknownThe final status of the SMS cannot be determined.Messaging
3040Queued by gatewayThe SMS gateway has queued the message.Messaging
3041Carrier rejected - temporary problemThis error is generated if there is an error on the carrier or operator side that is temporary and the message can be retried.Messaging
3042Carrier rejected - permanent errorThis 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
3043Error on gateway - temporary errorThis error is generated if there is an error on Telesign's partner side that is considered temporary and the message can be retried.Messaging
3044Error on gateway - permanent errorThis 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
3045Parameters problemOne or more parameters used in the request is not supported.Messaging
3046Message blocked by subscriber action or requestThe end user has blocked receiving SMS with their carrier plan or by request or from the particular short code used.Messaging
3047Subscriber low on creditThe end user exceeded their spending limits and cannot receive SMS.Messaging
3048Roaming errorEnd user cannot receive SMS because their device that receives the messages is roaming.Messaging
3049Mobile number portability errorSMS failed because ported combinations are unreachable.Messaging
3050Subscriber absentThe operator/carrier is temporarily unable to reach the end user's device.Messaging
3051Suspected spamThis message is considered to be spam by carrier or operator.Messaging
3052Message blocked by your requestThis 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
3053Message blocked by TelesignTelesign blocks a message if it is being sent to a phone number that is on a global blocklist.Messaging
3054Message cannot be sent to RBM provider - parsing errorTelesign’s RBM (Rich Business Messaging) partner encountered a temporary problem while sending this message. Please try again.Messaging
3055Delivery channel not supported by the end user's deviceThe end user's device does not support the channel used for delivery. FinalMessaging
3056Message failed to deliver in specified fallback timeDelivery could not be confirmed on this channel within the fallback window; triggers the next channel (if any) to send. (Intermediate)Messaging
3057Invalid source addressThe message requires a source address. Verify that one is provided and correct.Messaging
3058The requested API host is not allowed for this customer_idMessaging
3059Exceeded number of elements for rich cardMessaging
3061Media size exceeds the limitMessaging
3062MMS not supportedMessaging
3071Unverified phone_number requested for trial account.Messaging
3073Insufficient funds in prepaid walletMessaging
3100Unknown 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
3101Invalid value for parameter phone_number: {phone_number}Phone number is too long, too short, or contains non-digit values. (Intermediate)Messaging
3102Invalid 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
3103Unsupported value for parameter external_id: {external_id}The value of parameter external_id is longer than 100 or contains non-ASCII characters. (Final)Messaging
3104Invalid 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
3105Invalid value for parameter originating_ip: {originating_ip}Parameter originating_ip is improperly formatted. (Final)Messaging
3106Invalid value for parameter callback_url: {callback_url}The value of parameter callback_url is empty. (Final)Messaging
3107Invalid country code for parameter phone_numberMessaging
3108Invalid value for parameter messageMessaging
3109Invalid value for parameter sender_idMessaging
3110Invalid requestThe API request or its JSON payload is improperly formatted. (Final)Messaging
3112Specified template does not exist for selected channelMessaging
3113Invalid value for parameter channel: {channels}The value of the parameter channels contains the same channel more than once or is improperly formatted. (Final)Messaging
3114Specified message type not allowed outside of conversation windowMessaging
3115Destination phone number not in coverageMessaging
3200{channel} channel is not enabled for customerThis channel is not enabled for this customer. (Intermediate)Messaging
3202Fallback is not enabled for Customer IDMultiple channels are specified in the request, but fallback is not enabled for this customer. (Intermediate)Messaging
3203Callback URL parameter not enabled for Customer IDUsing callback_url in the API request is not allowed for this customer. (Final)Messaging
3204Rate limit exceededAllowed number of requests per second on Omnichannel API has been exceeded. (Final)Messaging
3205Rate Limit ExceededMessaging
3206Omnichannel Product not enabled for Customer IDOmnichannel product is not enabled for this customer. (Final)Messaging
3207Messaging exceeded transaction hard cap. Request denied.Messaging
3208Provider Account ID not foundMessaging
3209Phone number not registered for testingMessaging
3300Missing parameter channelsThe API request does not contain mandatory parameter channels. (Final)Messaging
3301Missing parameter channelThe value of the parameter channels does not contain any instances of the mandatory sub-property channel. (Final)
3302Missing parameter phone_numberThe API request does not contain the mandatory parameter phone_number. (Final)Messaging
3303Missing parameter messageThe API request does not contain the mandatory parameter message. (Final)Messaging
3304Missing parameter message_typeThe API request does not contain the mandatory parameter message_type. (Final)Messaging
3305Missing template specific parametersMessaging
3306Missing message parameters for specified channelMessage object doesn't contain required info for sending message through selected channel. (Intermediate)Messaging
3400Not authorizedNo permissions for this resource or authorization failed. (Final)Messaging
3405Missing required Authorization headerMessaging
3406CustomerID Account SuspendedMessaging
3408CustomerID Account Not FoundMessaging
3409Invalid source IP addressMessaging
3410Invalid Customer IDMessaging
3411Invalid API KeyMessaging
3412Required Authorization header is not in the correct formatMessaging
3413Not Allowed IP AddressMessaging
3500System UnavailableThe system is currently unavailable. The request should be resubmitted. (Final)Messaging
3601CustomerID Account Not FoundMessaging
4501SuccessVerification flow started in Silent Verify Initiate.Silent Verify API
4501Successfully verifiedDevice successfully verified on Silent Verify Finalize.Silent Verify API
4502The phone number does not matchUnable to verify the device because the phone number isn't associated with the device.Silent Verify API

Error codes

Error codeDescriptionProduct
-10001Invalid Request: ReferenceID Parameter: <reference_id>SMS Verify API
-10001Invalid Request: CustomerID Parameter: <customer_id>SMS Verify API
-10001Invalid Request: AuthenticationIDSMS Verify API
-10001Invalid Request: CustomerID/AuthenticationID Parameter: <customer_id>/<authentication_id>SMS Verify API
-10001Invalid Request: customer_id Parameter: <customer_id>SMS Verify API
-10001Not Allowed HostSMS Verify API, Voice Verify API
-10001CustomerID/ReferenceID not found Parameter: CustomerID/ReferenceID: <customer_id>/<reference_id>SMS Verify API
-10001CustomerID/ReferenceID not foundSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-10001Invalid parameter passedVoice Verify API, Number Deactivation, Smart Verify API
-10001Invalid Request: Missing parameter Parameter: TemplateBulk SMS
-10002Empty recipients listBulk SMS
-10003Max number of recipients exceededBulk SMS
-10004Reference ID expiredGet Status
-10009Invalid source IP addressSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API, Bulk SMS
-10033{phone_number} has not been verified for this trial account.SMS Verify API
-20001Invalid requestVoice Verify API, Number Deactivation, Smart Verify API
-20001Invalid Request: CustomerID Parameter: <customer_id>SMS Verify API
-20002This product is not enabled for this CustomerIDVoice Verify API, Number Deactivation, Smart Verify API
-20002This product is not enabled for this Customer ID.SMS Verify API, Bulk SMS
-20003This feature is not enabled for this Customer ID.Voice Verify API, Number Deactivation, Smart Verify API
-20004This product is not enabled for this country.Voice Verify API
-30000Invalid CustomerIDVoice Verify API, Number Deactivation, Smart Verify API
-30000Invalid Customer IDSMS Verify API, Bulk SMS
-30001Account suspendedVoice Verify API, Number Deactivation, Smart Verify API
-30001Customer ID Account Suspended.SMS Verify API, Bulk SMS
-30002Account not activatedVoice Verify API, Number Deactivation, Smart Verify API
-30003Account limit reachedVoice Verify API, Number Deactivation, Smart Verify API
-30004Missing required 'Authorization' headerSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-30005Required Authorization header is not in the correct formatVoice Verify API, Number Deactivation, Smart Verify API
-30005Required 'Authorization' header is not in the correct formatSMS Verify API
-30006Invalid signatureSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-30007Missing required 'Date' or 'x-ts-date' headerSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-30008Invalid X-TS-Auth-Method headerVoice Verify API, Number Deactivation, Smart Verify API
-30008Invalid 'x-ts-auth-method' header.SMS Verify API
-30009Date or X-TS-Date header is not RFC822 compliantVoice Verify API, Number Deactivation, Smart Verify API
-30009'Date' or 'x-ts-date' header is not RFC822 compliantSMS Verify API
-30010'Date' or 'x-ts-date' header is not within tolerable rangeSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-30011X-TS-Nonce header value is either too long or too shortVoice Verify API, Number Deactivation, Smart Verify API
-30011'x-ts-nonce' header value is either too long or too shortSMS Verify API
-30012'x-ts-nonce' header value has been used recentlySMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-30013Invalid ReferenceID for Verify CompletionCompletion, Get Status
-30015Invalid API KeySMS Verify API
-40001Status unavailableGet Status
-40002Not authorizedVoice Verify API, Number Deactivation, Smart Verify API
-40004Resource not foundVoice Verify API, Number Deactivation, Smart Verify API
-40005Method not allowedVoice Verify API, Number Deactivation, Smart Verify API
-40006Bad RequestBulk SMS
-40007Rate limit exceededVoice Verify API, Number Deactivation, Smart Verify API, SMS Verify API
-40007Rate Limit ExceededSMS Verify API, Bulk SMS
-40008[Product method] exceed transaction hard cap; Request deniedSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-40008Verify SMS exceeded transaction hard cap. Request denied.Bulk SMS
-40009Phone number not supportedSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-40023Number Deactivation
-40025Message blocked by TelesignBulk SMS API
-50001Max retries limit reachedSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50002Mobile 2FA registration errorSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50003Mobile device stamp drift too largeSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50051Invalid hashcash submittedSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50052Unmatched registration initiate requestSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50054Invalid API keyVoice Verify API, Number Deactivation, Smart Verify API
-50055Inactive API keySMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50056Inactive applicationSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50057Invalid verification codeSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50058Application is not registered for push notificationSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-50059Status not available
-60001Phone ID Contact data not foundPhone ID
-60002Mobile 2FA registration warningSMS Verify API, Voice Verify API, Number Deactivation, Smart Verify API
-90001System unavailable; please try again laterVoice Verify API, Number Deactivation, Smart Verify API
-90001System Unavailable, please try again later.SMS Verify API, Bulk SMS
10000System unavailable, please try again later.Silent Verify API, SMS
10002x-ts-nonce header value has been used recentlyAll
10003x-ts-nonce header is either too long or too shortAll
10004Date or x-ts-date header is not within tolerable rangeAll
10004Bad requestSilent Verify API
10005Date or x-ts-date header is not RFC822 compliantAll
10006Invalid x-ts-auth-method headerAll
10007Missing required Date or x-ts-date headerSMS
10008Invalid signatureAll
10009Missing required Authorization headerAll
10009Invalid value for parameter messageSMS
10010CustomerID Account SuspendedAll
10011Invalid value for parameter reference_idAll
10012This feature is not enabled for this CustomerIDPhone ID, Intelligence, SMS
10013Invalid Request. CustomerID Account Not FoundPhone ID, Intelligence
10014Invalid source IP addressPhone ID, Intelligence, SMS
10015Invalid Customer IDPhone ID, Intelligence, SMS
10017Customer ID / Reference ID not foundPhone ID, Intelligence, SMS
10019Rate Limit ExceededPhone ID, Intelligence, SMS, Silent Verify
10020Messaging exceeded transaction hard cap. Request denied.Phone ID, Intelligence
10020Generic messaging exceeded transaction hard cap. Request denied.SMS
10021The product is not enabled for this country.SMS
10022Invalid API KeySMS
10028Required Authorization header is not in the correct formatSMS
10031Not Allowed IP AddressSMS
10032Request blocked due to this number appearing on a Telesign blocklist.Phone ID, Intelligence
10033{phone_number} has not been verified for this trial account.SMS
10033Unverified phone_number requested for trial account.Intelligence, Phone ID
10035The requested API host is not allowed for this customer_idSMS
10036Reference ID expiredSMS
10039Internal server errorSilent Verify API
11000Invalid value for parameter phone_numberPhone ID, Intelligence, SMS, Silent Verify API
11001Invalid country code for parameter phone_numberPhone ID, Intelligence, SMS
11002Invalid value for parameter account_idIntelligence
11003Invalid value for parameter account_lifecycle_eventPhone ID, Intelligence, SMS
11004Invalid value for parameter callback_urlSMS
11005Invalid value for parameter customer_idPhone ID, Intelligence
11006Invalid value for parameter device_idIntelligence
11007Invalid value for email_addressIntelligence
11009Invalid value for parameter messageSMS
11010Invalid value for parameter originating_ipPhone ID, Intelligence, SMS
11011Invalid value for parameter reference_idPhone ID, Intelligence, SMS
11013Invalid value for parameter sender_idSMS
11016Invalid value for parameter external_idSMS
11017Invalid value for parameter message_type.SMS
11024Invalid value for parameter phone_number_1SMS
11025Invalid value for parameter phone_number_2SMS
11027Invalid value for parameter integration_name.SMS
11034Invalid value for parameter dlt_template_idSMS
11035Invalid value for parameter dlt_entity_idSMS
12000Missing required parameter phone_numberPhone ID, Intelligence
12000Missing Required Parameter phone_numberSMS
12003Missing required parameter account_lifecycle_eventIntelligence
12009Missing Required Parameter messageSMS
12017Missing Required Parameter message_typeSMS
40001Request timeoutSilent Verify API
40002Not authorizedSilent Verify API
40003No end client data found on recordsSilent Verify API
40004The required parameter 'verification' is missing from the requestSilent Verify API
40010Not in coverage. The phone number being verified is not within the provider's network.Silent Verify API
45005Error 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
45006Error 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
45010Provider 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
50054Invalid API KeySMS
50055Inactive API KeySMS
50056Inactive AppSMS