Mobile SasaDocs
Open portal

Quickstart

From nothing to a delivered SMS in about five minutes. One portal visit to get credentials, then everything else happens over the API.

1. Create an account and get a token

  1. Register at account.mobilesasa.com (free, no card needed). Verifying your phone credits a few trial SMS, so you can watch a message arrive before paying for anything.
  2. Open API Tokens in the sidebar and create a token. Copy it immediately. It is shown once.
  3. Note your approved sender ID (Sender IDs page). New accounts start with trial access to the shared MOBILESASA sender: sends reach your own registered number, which is exactly what the free trial SMS are for. Request full access (Settings, Default Sender — one document) to message any number, or register your own branded name.

Keep tokens server-side

A token is a password. Never embed it in a mobile app, browser JavaScript, or a public repository. Calls should always come from your backend.

2. Send your first message

# 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! Your Mobile Sasa integration works."
  }'

3. Read the response

Success
{
  "status": true,
  "responseCode": "0200",
  "message": "Accepted",
  "messageId": "3c51beb1-a674-41d0-9e45-f5581418fb56"
}

status tells you whether the request was accepted; responseCode is a stable machine-readable code (full list in Responses & errors). Delivery to the handset is asynchronous. Track it with delivery reports.

4. Go further

Phone number formats

All of these are accepted and normalised to E.164 for you: 0712345678, 254712345678, +254712345678. Invalid numbers are rejected with a validation error rather than billed and dropped.