Eastern Bypass, Utawala. Grey Park Heights, 3rd floor, Suite C3 +254 717 581 105 info@satas.co.ke
Developer guide

SMS API vs SMPP: which should you use?

Two ways to connect your own system to a bulk SMS platform: what each one is, how they differ and how to choose.

If your website, app or CRM needs to send SMS on its own, for example one-time codes, order updates or payment reminders, it has to connect to an SMS platform. There are two common ways to do that: an SMS API over HTTP, or an SMPP connection. Both can send messages and report delivery. They differ in how much work they take to set up and what kind of system they suit.

What is an SMS API?

An SMS API (often called a REST or HTTP API) lets your system send a message by making a normal web request, the same kind of request a browser makes. Your code sends the phone numbers and the text, signed with an API key, and gets an answer back straight away.

Most programming languages and tools can make web requests, so an SMS API is usually the quickest way to start. It works well for websites, mobile app back ends, CRMs, accounting systems and scripts.

What is SMPP?

SMPP (Short Message Peer-to-Peer) is the protocol that mobile networks and SMS companies use to pass messages between each other. Instead of one web request per send, your system opens a connection to the SMS platform, called a bind, keeps it open and sends messages through it. Delivery receipts come back over the same connection.

SMPP is built for systems that already speak it, such as messaging gateways, aggregators and some banking or telecom software, and for steady high volumes.

The main differences

SMS API (HTTP)SMPP
How you connectA web request for each sendA connection that stays open
Setup effortLow: an API key and a few lines of codeHigher: an SMPP client, account details and connection settings
Delivery reportsCheck message status, or receive a webhookDelivery receipts arrive on the open connection
Best forWebsites, apps, CRMs, scriptsGateways, aggregators, systems that already use SMPP
Skills neededAny web developerSomeone familiar with SMPP

Speed and volume

An open SMPP connection avoids the overhead of starting a new web request for every message, which is why it is popular for large, continuous traffic. For most businesses, an SMS API is fast enough: you can send to many numbers in one request, and campaigns of thousands of messages run without problems. In both cases the platform sets a sending rate for your account, so very large volumes are planned with your provider either way.

Delivery reports

Both methods tell you whether a message was delivered. With an API you can look up the status of sent messages, or give the platform a webhook address so it calls your system when the status changes. With SMPP the platform sends a delivery receipt back over your connection. Remember that "delivered" means the message reached the phone, not that the person read it.

Which one should you choose?

How SATAS SMS Pro supports both

SATAS SMS Pro offers both connection types on the same account and the same prepaid credits:

Messages sent either way use your registered sender ID and are charged at the same price per SMS. If you are new to bulk messaging, start with our step-by-step guide to sending bulk SMS in Kenya, and see the developer page for the wider SATAS API.

Before you go live

Common questions

What is the difference between an SMS API and SMPP?

An SMS API sends each message with a web request and is quick to set up. SMPP keeps a connection open between your system and the SMS platform and is mainly used by gateways, aggregators and systems that already support it.

Is SMPP faster than an SMS API?

An open SMPP connection avoids starting a new web request for each message, so it suits large continuous traffic. For most business campaigns an SMS API is fast enough, and in both cases the platform sets a sending rate for your account.

Do I get delivery reports with both?

Yes. With an API you can check message status or receive a webhook; with SMPP, delivery receipts come back over the open connection. Delivered means the message reached the phone, not that it was read.

Does SATAS SMS Pro support SMPP?

Yes. SMPP accounts are set up on request, on port 2775, with transmitter, receiver and transceiver binds. The same account can also use the REST API.

Which should a small business choose?

Usually the SMS API: it only needs an API key and a few lines of code, and works with websites, apps and CRMs.

Connect your system to SMS Pro

Open an account and create an API key, or ask us to set up an SMPP account for your gateway.