Mobile Sasa Developer Documentation
Everything you need to integrate SMS, WhatsApp, USSD and two-way shortcodes into your application, whether you write your first API call today or push a million messages a month.
Mobile Sasa is an API-first messaging platform. You can run your entire integration, from your first test message to production traffic, without ever opening the web portal, apart from one visit to create your account and API token. Everything documented here works with plain HTTP: if your language can make a POST request, it can send messages.
The 30-second picture
# Paste your token once (it starts with mbs_):
export MOBILESASA_TOKEN="mbs_your_token_here"
curl -X POST https://api.mobilesasa.com/v1/send/message \
-H "Authorization: Bearer $MOBILESASA_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"senderID": "MOBILESASA",
"phone": "0712345678",
"message": "Hello from the Mobile Sasa API!"
}'That's a real, working call. Get a token from the portal (Quickstart walks you through it in five minutes), paste your token into the first line, and the message is on its way.
Pick your product
SMS API
Send single, bulk and personalised SMS to every Kenyan network, with delivery reports.
WhatsApp API
Broadcast Meta-approved templates from your own WhatsApp Business Account.
USSD
Drive dialled *657# sessions from your own backend with callback mode.
Shortcodes & Inbound
Receive keyword texts and two-way replies on your webhook in real time.
Email API
Send from your own verified domain. Transactional and bulk, billed per recipient.
Reminders
Recurring scheduled SMS and birthday/anniversary messages on autopilot.
Account & Wallet
Balances, audit ledgers, and M-Pesa wallet top-ups for service fees.
SMPP
Bind directly over SMPP 3.4 for high-throughput transactional traffic.
API stability
The /v1/ and /v2/ SMS endpoints are frozen: their URLs, request fields and response shapes never change. An integration you write against them today keeps working, permanently. Newer platform resources (WhatsApp, exports, contact management beyond the frozen group endpoints) live under /api/v1/ and use scoped mbs_ tokens. See Authentication.
New to APIs?