SMS - Get started

This page explains the basic usage of Telesign SMS.

General requirements

  • Resource:
  • Authentication: Basic (easiest to implement) or Digest
  • Encoding: Accepts only UTF-8 unicode characters as inputs.
  • Accepts: application/x-www-form-urlencoded
  • Required Headers: Content-Type - application/x-www-form-urlencoded

Try it

For instructions on how to send your first SMS, see SMS - Try it.

For a list of available parameters, see the POST /v1/messaging page.

Obtain transaction status results

There are two ways to check the status of your transactions:

  • Query the API - Get the status of an individual transaction by querying the SMS API, available for up to 12 hours after sending your message.
  • Receive callback service notifications - Receive status notifications from Telesign about multiple transactions, at a URL that you provide. We recommend using this when you have a high volume of transactions.



If you need to receive messages back from customers, a related service that we offer is Inbound SMS. For more about this service, see Inbound SMS. Contact our Customer Support Team to enable this feature.

URL shortener

To help shorten your text messages, Telesign provides a complimentary URL shortening service. You can read more about how to enable it at URL shortener.


This section provides examples of a request and response using Telesign SMS.


Authorization: Basic 12345678-9ABC-DEF0-1234-56789ABCDEF0:Uak4fcLTTH/Tv8c/Q6QMwl5t4ck=
Content-Type: application/x-www-form-urlencoded; charset=utf-8
phone_number=15551212&message=Your message here.&message_type=MKT


HTTP/1.1 200 OK
Content-Type: application/json
   "reference_id": "0123456789ABCDEF0123456789ABCDEF",
   "status": {
      "code": 290,
      "updated_on": "2017-31-03T14:51:28.709526Z",
      "description": "Message in progress"


For SMS compliance best practices, please refer to the articles in the Compliance section in our Support Center.

Did this page help you?