In this guide · 5 sections
If you’ve looked at SMS providers in Kenya, you’ve probably seen “SMPP” listed next to “API”. Here’s what it means, and whether your business needs it.
SMPP in one paragraph
SMPP stands for Short Message Peer-to-Peer. It’s an open, long-established protocol that messaging systems use to exchange SMS with gateways and mobile networks. Instead of making a separate web request for every message, your system opens a connection to the SMS gateway, keeps it open, and sends and receives messages over it continuously.
How an SMPP connection works
- Connect and bind. Your SMPP client connects to the gateway’s host and port and logs in (“binds”) with a system ID and password. A bind can be for sending, receiving or both.
- Submit messages. Your system sends each SMS as a submit_sm request with the sender ID, recipient and text. The gateway replies with a message ID.
- Receive delivery receipts. When the network confirms delivery or failure, the gateway sends a deliver_sm back over the connection carrying the receipt. Inbound messages from customers arrive the same way.
- Stay connected. The two sides exchange small “enquire link” messages to check the connection is alive, and your client reconnects if it drops.
SMPP vs an HTTP SMS API
| HTTP API | SMPP | |
|---|---|---|
| How you send | One web request per message or batch | A persistent connection |
| Effort to build | Low: any language that can make an HTTPS request | Higher: needs an SMPP client and connection handling |
| Delivery reports | Posted to your callback URL | Returned over the connection |
| Best for | Websites, apps, campaigns, OTPs and alerts | High, steady volumes and messaging platforms |
Does your business need SMPP?
Probably not, if you’re sending campaigns from a dashboard or a few thousand notifications a day from an app. An HTTP API is quicker to build and easier to maintain. SMPP is worth it when:
- you already run a messaging platform or core system that speaks SMPP, as many banking and telecom systems do;
- you send high, continuous volumes and want to avoid the overhead of a web request per message;
- you’re a software company or reseller sending on behalf of many clients.
What to ask a provider before connecting
- Which Kenyan networks are reachable over the connection, and at what rates?
- Which sender IDs will be available on the bind, and how are they registered?
- How are delivery receipts formatted, and how long are they kept?
- Will they test the connection with you before you move live traffic?
Ndovubase offers both an HTTP SMS API and SMPP connections on the same account. Tell us your volumes and platform and we’ll recommend the simpler option that works.
