Africa's Talking SMS integration: bulk SMS, alerts and USSD
Africa's Talking SMS integration lets your system send transactional and bulk SMS (receipts, OTPs, reminders) and receive delivery reports through Africa's Talking's API. You need an Africa's Talking account, airtime/credit, and ideally a registered sender ID. Mjengo Corporate integrates it in a few days; sender ID approval can take longer.
Updated
| Product | What it does | Typical use |
|---|---|---|
| SMS | Send single or bulk messages; receive delivery reports | Receipts, OTPs, reminders, alerts |
| Sender ID | Show your business name instead of a number | Trust and brand recognition |
| Short code / two-way SMS | Receive replies from customers | Opt-outs, keyword replies, surveys |
| USSD | Menu-based service on any phone, no data needed | Balance checks, registrations, simple self-service |
| Airtime | Send airtime programmatically | Rewards and incentives |
How does the integration work?
Your server calls Africa's Talking's SMS API with your username, API key, recipients and message. The API responds immediately with a status per recipient, and the final delivery status arrives later at your delivery report callback. For two-way SMS and USSD, Africa's Talking calls your server when a customer replies or dials your code, and your server responds with the next message or menu.
What do you need?
- An Africa's Talking account and a production app with an API key.
- Credit loaded on the account.
- A sender ID registered for your business name. Approval involves the mobile networks, so start early.
- For USSD or short codes: the relevant service code application.
- A public HTTPS callback for delivery reports and incoming messages.
Common SMS integration pitfalls
- Ignoring delivery reports. "Sent" doesn't mean "delivered". Store the final status and retry or alert on failures.
- Message length. Long messages are split into several billable parts; special characters can shorten the limit.
- No provider fallback. If one gateway has an outage, critical messages like OTPs should fail over to another.
- Sending without opt-out handling for marketing messages.
- Phone number formats. Normalise to international format (+254…) before sending.
How Mjengo Corporate builds SMS integrations
Netily, our ISP billing platform, sends payment reminders, receipts and reconnection notices through any of 12 supported SMS gateways, including Africa's Talking, Advanta, Celcom Africa, Twilio and Infobip. We bring that design to client systems: one messaging module, several interchangeable providers, delivery tracking, and templates your team can edit without a developer.
Frequently asked questions
How long does Africa's Talking integration take?
The API integration takes a few days. Sender ID approval depends on the networks and can take longer, so we start the application on day one.
Can I switch SMS providers later?
Yes, if the system is built with a provider-agnostic messaging layer. Netily supports 12 SMS gateways this way, and we build client systems the same way.
SMS or WhatsApp for customer notifications?
SMS reaches every phone without data and suits OTPs and receipts. WhatsApp allows richer messages and two-way chat. Many businesses use SMS for critical alerts and WhatsApp for conversations.
