MobileSasa 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.

MobileSasa 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

Your first message
curl -X POST https://api.mobilesasa.com/v1/send/message \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "senderID": "MOBILESASA",
    "phone": "0712345678",
    "message": "Hello from the MobileSasa API!"
  }'

That's a real, working call. Get a token from the portal (Quickstart walks you through it in five minutes), replace YOUR_API_TOKEN, and the message is on its way.

Pick your product

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?

Follow the Quickstart top to bottom — it assumes nothing beyond being able to copy a command into a terminal. Experienced developers can jump straight to the endpoint reference for their product.