We created a new viewing experience for our SMS API documentation. It's now all in one central location. Click here to check it out!

 curl https://api.transmitsms.com/send-sms.json \
-u {APIKey}:{APISecret} \
-d 'message=Hi guys' \
 -d to=1234567890

Our simple REST API allows you to get up and running in minutes, with just a single line of code. For advanced users, dig deeper into our technology and check our reference guides for more detailed functions and calls. We also offer a number of client libraries and code samples in order to make your experience using the API suite as clean as possible.

Sending Messages

-d 'message=Hello' \ 
-d to=1234567890 \
-d list_id=12345 \

You can elect to pass us the recipient numbers from your database each time you make a call, or you can elect to store recipient data in a Contact list and submit only the list_id to trigger the send.

This is best for large databases. To add a list please refer to the add-list call.

Getting Delivery Reports

http://yourdomain.com/yourapp?message_id=12345&mobile=123456890 &datetime=2013-06-14+0&status=delivered

DLR's or Delivery Receipts, are notifications received from the carriers relating to the success or otherwise of an attempted SMS Delivery. Your DLR Callback URL is the default URL we post incoming DLR's to.

You can also set the DLR Callback URL separately for individual messages. This is done using a parameter on the send-sms call.

Getting Replies

http://yourdomain.com/yourapp?message_id=12345&mobile=123456890 &datetime=2013-06-14+0&response=Thankyou

The default Reply Callback URL is used to manage incoming SMS. This is the default URL we will post all incoming messages back to.

You also can set the Reply Callback URL separately for individual messages. This is set as a parameter on the Send-SMS call