Create account
Bulk messaging for Zimbabwe

Make messaging your superpower.

SMS, WhatsApp and email from one dashboard and one API. Send to a hundred people or a hundred thousand, see the cost before you commit, and know what actually arrived.

Create accountRead the docs

Fast, scalable messaging — with receipts. SMS from $0.014 · local and international.

What you get

Four things Sendai does properly.

No feature soup. One platform that sends, and shows its working.

Three channels, one account

SMS, WhatsApp and email from the same balance — pick the channel per message or per campaign.

SMSWhatsAppEmail

Campaigns without the chaos

Upload a spreadsheet, write the message once, schedule it, and send to a hundred or a hundred thousand — one call, one price, one report at the end.

A sub-account for every brand

Split clients, teams and brands into sub-accounts — each with its own balance, its own reports and its own sender names. Then pick whose name each campaign goes out under.

OTP verification codes, by API

One call from your app and the code is on its way — six digits always fit a single SMS segment, and every code keeps its own delivery record, so “I never got it” becomes a lookup. You'll be plugged in within an afternoon.

Stop guessing. Start knowing.

Most gateways stop at “sent”. Sendai follows every message to the handset — you see what arrived, what didn't, and exactly what each one cost.

I run campaigns

Send like a team of ten.

No developer required. Upload your contact list — a spreadsheet is fine — write the message once, and schedule it for the right morning.

  • See the full cost before you press send
  • Choose which sender name each campaign goes out under
  • Hand your client a delivery report, not a screenshot
  • Stuck mid-campaign? AI-assisted support answers right away
See the two steps →
I build products

One API. Agents built in.

A REST API you can hold in your head — sends, sender names, balances — with webhooks that call you back instead of making you poll. Claude, Cursor and any MCP client plug straight into our hosted MCP endpoint.

# one key, one call — this is the whole send
curl -X POST \
  https://api.sendai.co.zw/api/v1/sms \
  -H "Authorization: Bearer sk_live_4c8e…" \
  -d '{ "to": "+263 77…", "from": "MAYABAKERY",
        "message": "Your code is 482019" }'
Read the docs →
Receipts

Receipts, not promises.

Anyone can quote a percentage. Sendai shows you each message's record — what went out, what arrived, and what it cost.

3

Local + International networks

Econet, NetOne and Telecel — every mobile handset in Zimbabwe from one account. Sending beyond? International routes are live through our carrier partners.

Every message keeps a record.

Not “sent, good luck” — the actual life of the message, kept per recipient.

// sample — swap for a live record
$0.014

Where SMS starts

Rates vary by network and destination — and the exact cost of your send is priced before you commit, held from balance, and returned with the receipt.

Prepaid. No surprises.

Every send places a hold on your balance, and the exact cost comes back with the send. If the balance can't cover it, nothing goes out at all — never half a campaign.

Support that actually answers.

First-class support with AI-assisted agents on the front line — instant answers at 2am or mid-campaign, and a human never more than a step behind.

Need replies? Two-way works.

Inbound SMS is available per account — tell us what you're building and we'll switch it on for yours.

From signup to sending in about half an hour.

— how onboarding actually works

Bring your AI agent.

Sendai hosts an MCP server, so Claude, Cursor or any MCP client can send from your account — same key, same balance, same delivery record.

send_sms · send_bulk_sms · get_sms · get_balance · list_sender_ids
20+

Years in telecoms

Sendai is engineered and run by people with more than twenty years in local and international telecoms. This is the platform we always wanted to run.

Built for OTP codes.

A six-digit verification code always fits a single SMS segment — the least forgiving traffic there is, at its smallest price.

2

Endpoints to learn

One for a single message, one for a whole list. That is the entire sending API.

Getting started

Two steps. Then send.

Register, upload your KYC documents — that's the whole application. The networks approve in about 30 minutes.

  1. Create your account

    Register, verify your email, and name your sender ID right in the signup form. You're in the dashboard straight away.

  2. Upload your KYC documents

    Drop them in the dashboard — that's it. The networks take it from there, usually in about 30 minutes.

While the half hour ticks by, you already have everything: the API and docs, contact-list uploads, and a composer that prices your campaign before you send.

Go deeper

The docs pull no punches.

Start where you like — it's one key and two endpoints all the way down.

Quickstart

Your first message in a handful of lines — one key, one call, a real response you can read.

Read the docs

Webhooks

message.delivered and message.failed, signed and sent to your server — your system hears about a delivery instead of asking.

Read the docs

Bulk sends

One call, a whole list, priced as one send — with per-recipient results and a report at the end.

Read the docs