SMS API | Send SMS | Overview

Sending SMS is easy. SMS One-way allows you to send SMS worldwide to any phone number. After setting up your account in your tyntec you are able to send messages instantly.

1. Setup SMS One-way (Send SMS)

Login to your tyntec first and navigate to the SMS section. Click ‘Add a new account’ near the top left of your screen. You will be prompted to select a product. Select ‘SMS one-way (SMS-MT)’ to set up your SMS one-way account.

To complete the setup of your account, you must choose:

  • Product
  • API / Protocol
  • Source IP Address #1

You may also add a second ‘Source IP Address.’

For the RESTful API you can also add a ‘Respond back URL.’


After adding the SMS one-way account, you will receive an email with your individual user account credentials. Go ahead and check your email.

The email with your credentials looks like the image below.


2. Your first message request

For this part, you'll probably need some developer's expertise.

Let's try submitting a message request. You'll need to use your Linux command line. Using the snippet below, replace “username” and “password” with the credentials we sent to you via email:

curl -i -X POST
-H "Content-Type: application/json"
-u username:password
-d '{"from":"username", "to":"+441234567","message":"hello

If everything worked fine, you should get a response confirming your request with the request ID. You can use the request ID to check the status of the message afterwards.

The response should look similar like this.

HTTP/1.1 200 OK

If you’re using Windows, you can try sending an SMS from a REST client that you’re currently using or with Postman, Advanced Rest Client, etc.

3. IT Architecture

The following illustration shows how sending a SMS works. 


1. Enterprise sends a request to tyntec with senderID , content and phone number via API
2. tyntec identifies the request and delivers the message using the best available route defined by our routing engine
3. tyntec provides the customer with a delivery status response containing the customer request ID, the size of your message and a list of respective message IDs.