Get started with docs

Welcome to Telesign's product documentation. Here you will find details to learn about, try, and implement Telesign's products.

Individual products are listed in the left-hand navigation of this site with product details, process guides, and tutorials for common use cases.

Here are some processes and tools to help you get started:

Access your authentication credentials

Before you begin testing, ensure you have Telesign authentication credentials (API Key and Customer ID).

Need help finding your credentials? View the instructions in the support article How do I find my Customer ID and API Key?

Test without code using the API Explorer

Our API Explorer allows you to learn about an API by sending a request directly from our documentation site instead of writing code. For ease of use, some request parameters are pre-populated with default values for you. If you want to experiment, you can change these parameter values.

Our reference pages for endpoints each include an API Explorer. Use the sidebar to navigate to your product's reference page. The center column provides information about general requirements, parameters, responses, and error and status codes. You may need to select items to expand nested content. Once you fill in the requested information, you can head over to the right-hand column to use the Try it feature of the API Explorer. There, you will be able to select your choice of coding language or select request or response examples to view.

Test with code using a tutorial

To try our products with code using your preferred programming language, select which of our tutorials you want to follow, then install an SDK in your favorite language (C#, Java, Node.js, PHP, Python, or Ruby).

Create a free Trial account

Create a free Telesign Trial account and receive a unique API key and Customer ID, as well as $5 in complimentary test credits. With a Trial account, you can use your authentication credentials and credits to test some of Telesign’s core products: SMS, SMS Verify, Intelligence, and Phone ID.

Learn more about how a Telesign Trial account works.

View codes, languages, and time zones

Codes are potential values included in Telesign API responses. View country and dialing codes as well as codes for supported languages, phone number cleansing, use cases for SMS Verify API and Voice Verify API, phone types, phone type override reasons, and time zones.

Telesign returns status and error codes in API responses. Understand how they are assigned and some best practices, and view all status and error codes.

Lease a number or sender ID

Telesign offers a wide range of localized phone numbers, caller IDs, and sender IDs for sending outbound messages and voice calls. You can lease a phone number, caller ID, or sender ID directly from Telesign by submitting a request specifying your expected use cases and desired delivery regions.

Receive status updates about your requests

Use Telesign's Transaction Callback service to receive status updates about your requests for select Telesign products. Learn more about how to authenticate your callbacks.

Set up automated failovers for outbound messages

Telesign's automated failover is enabled for any 500-509 HTTP responses for all products except for Voice. Failover will retry all available Telesign locations prior to sending a client response. While this failover is very rarely triggered, you can disable it per request on any product.

Connect to Telesign using the SMPP protocol

The SMPP (Short Message Peer-to-Peer) protocol is an open, industry standard protocol designed to provide a flexible data communications interface for the transfer of short message data between various entities. View the necessary technical details and connect to Telesign using the SMPP protocol.

Integrate with Okta using the Okta telephony inline hook

Telesign offers easy migration and scalability for existing Okta customers choosing a new telephony service provider to send one-time passcodes (OTPs). Use our pre-built, no-code inline hook solution or code your own integration using our full-service APIs to continue sending OTPs via SMS and voice.