Email API

Transactional and bulk email sent from your own domain — no SMTP servers, no IP-reputation headaches, billed per recipient from your email balance.

Endpoints live under /api/v1/ with a scoped mbs_ token or JWT. Sending happens from a verified domain that our team onboards for you, so deliverability (SPF, DKIM, IP reputation) is handled once and stays handled.

Onboarding — one conversation, three steps

Tell support the domain you want to send from (e.g. mail.yourbrand.co.ke). We register it with the email provider and hand back a short list of DNS records.
Publish the DNS records — or let us manage the domain and DNS entirely, which most customers prefer; you never touch a nameserver.
We verify, the domain flips to verified, and every address on it can send.

Your domains

GET/api/v1/email/domains

curl "https://api.mobilesasa.com/api/v1/email/domains" \
  -H "Authorization: Bearer $MOBILESASA_TOKEN"

Response — 200

{
  "success": true,
  "data": [
    {
      "uuid": "7c2e91d4-…",
      "domain": "mail.yourbrand.co.ke",
      "status": "verified",
      "default_from": "[email protected]",
      "verified_at": "2026-07-10T08:12:00Z"
    }
  ]
}

Billing

Parameters

Field	Type	Required	Description
1 unit / recipient	email_balance	No	Every accepted recipient costs one email unit at your team's email rate — check balances on the Account & Wallet page. Reserved up front; a send that can't be covered is rejected whole with no partial billing.
Suppressed = free	protection	No	Addresses that hard-bounced or complained are auto-suppressed: future sends skip them and never bill them.
Delivery tracking	webhooks	No	Statuses flow back automatically — `sent → delivered / bounced / complained` — visible on the messages endpoint.

Why not run your own SMTP?

Shared and self-hosted SMTP IPs get blacklisted, and un-blacklisting eats weeks. Sending through the platform's provider pool means your mail rides infrastructure whose reputation is actively maintained — you keep your brand's domain, we keep it deliverable.