TABAN SMS · HOSTED API

SMS for your app,
already hosted.

Taban operates the SIM, phone, Android gateway, server, and carrier connection. Your application only needs an API key and a secure backend request.

Your applicationBackend API request
Taban SMS serviceHosted gateway + API
Our SIM & phoneCarrier delivery
01 · REQUEST ACCESS

Open a service account

You do not need to buy a SIM, install an Android app, or host an SMS gateway. After approval, Taban creates a Test or Live developer agent in the admin panel and gives you one API key.

01

Tell us about your app

Send your company name, application name, country, expected monthly volume, sender identity, and use case.

02

Receive a Test key

Use a Test key first. Test requests return a simulated message ID and do not send a carrier SMS.

03

Move to Live

After approval, Taban creates a Live agent. Store its key server-side and use it to send through the Taban SIM.

02 · QUICKSTART

Connect step by step

Follow these steps in order. Everything below happens in your application; Taban operates the sending infrastructure.

  1. 1

    Receive a developer API key

    The Taban admin creates your developer agent. You receive a key beginning with tb_test_ for testing or tb_live_ for real SMS delivery. Save it immediately because it is shown only once.

  2. 2

    Choose where your request will run

    For a first test, use Postman. For your real application, call the API from your backend server. Never put the key in frontend JavaScript, a browser, or a mobile app.

  3. 3

    Use the exact API URL

    Your request must use POST https://api.taban.so/api/sms/v1/messages.

  4. 4

    Add the authorization header

    Add Authorization: Bearer YOUR_API_KEY. Replace YOUR_API_KEY with the complete key. Include the word Bearer and one space.

  5. 5

    Add the JSON message body

    Use raw JSON. Put the recipient in international E.164 format, including the country code, and add the message text.

  6. 6

    Send, read the response, and check Logs

    A Test key returns a simulated message ID. A Live key sends through the Taban SIM. If something fails, open Admin → SMS Developers → Logs and match the time, status, and error code.

03 · POSTMAN TEST

Test your key in Postman

Use a tb_test_ key first. Postman lets you confirm your key and request format before writing application code.

  1. 1

    Open Postman and create a request

    Open Postman and select New → HTTP Request. Save it in a collection such as “Taban SMS”.

  2. 2

    Select POST and enter the URL

    Choose POST and paste:

    https://api.taban.so/api/sms/v1/messages
  3. 3

    Configure authorization

    Open Authorization. Set Type to Bearer Token. Paste the complete key into the Token field. Do not type the word Bearer inside the token field—Postman adds it.

  4. 4

    Set the JSON body

    Open Body → raw, select JSON, and paste this. Replace the number with your own number in international format.

    {
  "phoneNumbers": ["+252XXXXXXXXX"],
  "textMessage": {
    "text": "Test message from Postman"
  }
}
  5. 5

    Click Send

    A successful Test response is normally 202 Accepted and includes test: true and a messageId. No real SMS is sent.

  6. 6

    Check the admin request log

    Sign in to Taban → Admin → SMS Developers, find the agent, and click Logs. You will see the result, HTTP code, latency, and message ID.

WHAT YOU NEED

Your app only needs HTTPS

Your team does not manage telecom hardware. Build your normal backend integration and let Taban handle the sending infrastructure.

  • A server-side application
  • A Taban developer API key
  • HTTPS access to the API
  • Recipient numbers in E.164 format
Keep the key server-side

Do not put API keys in frontend JavaScript, mobile apps, public repositories, or support tickets.

04 · SEND AN SMS

Move from Postman to your app

Once the Postman Test key works, copy the same URL, header, and JSON body into your backend application.

Taban SMS API
curl -X POST https://api.taban.so/api/sms/v1/messages \
+  -H "Authorization: Bearer tb_test_YOUR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"phoneNumbers":["+252XXXXXXXXX"],"textMessage":{"text":"Test message from Taban"}}'
Important: A successful response means Taban accepted the message. Delivery depends on the destination carrier.
05 · API REFERENCE

Hosted service endpoints

Use https://api.taban.so/api/sms/v1. The Taban gateway and SIM remain on our infrastructure.

POST/messages

Send an SMS using the API key created in the Taban admin panel.

GET/health

Check service availability through your normal monitoring process.

Track every request

Taban records the environment, HTTP result, response time, recipient count, message length, message ID, and failure reason. Open Admin → SMS Developers → Logs. SMS text and full phone numbers are never stored in these logs.

06 · TROUBLESHOOTING

Common problems and fixes

Do I need my own SIM or Android phone?

No. Taban operates the SIM, Android gateway, server, and carrier connection. You only integrate with the hosted API.

I received 401 invalid_api_key

Confirm the key is complete and active. A tb_test_ key must be used as-is. Do not add quotes, spaces, or the word Bearer inside the key. If the key was rotated, use the newest key.

I received 400 phoneNumbers_and_textMessage_required

In Postman, use Body → raw → JSON and include both fields: phoneNumbers as an array and textMessage.text as a non-empty string.

I received 429 daily_limit_reached

The agent reached its daily limit. Ask the Taban admin to increase the limit or wait for the next day.

I received 503 sms_service_unavailable

The key was accepted but the hosted gateway could not send. Open Admin → SMS Developers → Logs. If the error is gateway_credentials_missing, the Taban operator must configure the hosted gateway credentials.

Can I call the API from frontend code?

No. Call it from your backend so API keys are never exposed to users.

READY TO INTEGRATE?

Request your Taban SMS account.

Tell us what you are building and we will provide the correct Test or Live access.