Write to email@example.com.
Understand TeleSign Status and Error Codes
TeleSign returns error and status codes in API responses. Typically, status codes are three or four digits long, and go with the type of product you are using. Error codes are five digits long and may come back negative or positive.
How Status and Error Codes Are Assigned
Status codes are assigned to the various products as follows:
- 1xx - Voice Verify, old Voice (new Voice, which uses events and actions and which you must set up a server for does not use these codes)
- 2xx - SMS Verify, SMS
- 3xx - PhoneID, Score
- 20xx or 24xx - App Verify API
- 28xx - PhoneID add-ons
- 5xx - These may apply across products.
Error codes are applied across products. Review the Error Codes section of the All Status and Error Codes page for further details.
When coding, it is best to code against TeleSign’s error or status codes for a product, not an HTTP response. TeleSign may return error or status codes for the following HTTP responses:
You should check the API reference for your product to see which HTTP status codes return error and/or status codes.
TeleSign does not recommend coding against code descriptions or text strings, since these may be subject to change. Instead, code against the actual error code or status code.
HTTP Response Status Codes
TeleSign web servers use HTTP Response Status Codes to communicate the result of processing requests. The most common status codes returned by TeleSign web servers are:
|HTTP Status Code||HTTP Status Description||Description|
|201||The request has been fulfilled and has resulted in one or more new resources being created||No error|
|400||Bad Request||Invalid parameter passed|
|401||Unauthorized||CustomerID does not exist/Account suspended|
|403||Invalid Token||Parameter doesn’t match|
|404||Not Found||Invalid URI|
|429||Too Many Requests||Rate limit exceeded|
|500||Invalid Transaction||Transaction not attempted|
|503||Service Unavailable||System unavailable; try again later|