One API for SMS, WhatsApp and email
Send from your code in any language, follow every delivery, and reply to customers from one workspace. The price is shown before anything leaves.
import { randomUUID } from "node:crypto";
const res = await fetch(`${process.env.SAVARA_HOST}/api/v1/messages`, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SAVARA_API_KEY}`,
"Content-Type": "application/json",
"Idempotency-Key": randomUUID(),
},
body: JSON.stringify({
channel: "WhatsApp",
to: "+256770123456",
template: { name: "order_ready", language: "en", parameters: ["Amina", "1842"] },
consent: true,
}),
});
console.log(res.status, await res.json());Works with the stack you already use
Next.js
Express
Laravel
DjangoTry it here
Switch channels to see the sender, the message and the delivery event your team tracks in SavaraFlow.
Acacia Studio · Order #1842
Coverage and pricing
Pick a destination and type your message. Segments and cost update as you write, the same way the console quotes every send.
$0.0392 per message · includes the 12% service fee
SMS is live in Uganda on MTN and Airtel, with branded sender IDs.
Estimate based on public example rates. The console shows a live quote for your workspace before every send.
SMSWhatsAppEmailTeam inboxChannels
Start with one and add the others when your senders are ready. Same API, same wallet, same delivery logs.
Pickup alerts, reminders and one-time codes. Use a branded sender ID where your route allows it.
Connect your Meta business number, sync approved templates and bring every reply into the team inbox.
Send receipts and account notices through SavaraMail from an address on your own domain.
WhatsApp templates
WhatsApp business messages start from a template Meta has approved. Fill in the blanks and each customer gets their own message. Try changing the values.
order_ready · UTILITY · enHi {{1}}, your order {{2}} is ready. Collect it before {{3}} at {{4}}.
"template": {
"name": "order_ready",
"language": "en",
"parameters": ["Amina", "#1842", "6 pm", "Acacia Studio"]
}The workspace
Good morning, Amina
SMS, WhatsApp and email replies in one queue, with assignment and resolve states.
Import a list, clean duplicates and invalid rows, and see the batch price before you send.
Draft a reply, translate to Luganda or Swahili, or triage a conversation. Your agent always sends.
Trigger follow-ups from events with delays and conditions you control.
Top up with mobile money or card. Every send is quoted and reserved first.
Follow every attempt in delivery logs or receive signed status events.
Smart fallback
Turn on fallback when you message a contact. SavaraFlow tries your first choice, then moves through the other channels that contact agreed to until one gets through.
route: WhatsApp → SMS → EmailCSV bulk sending
Drop in a spreadsheet export. SavaraFlow fixes local numbers, merges duplicates and sets aside bad rows, then prices the batch before anything is sent.
| # | name | phone | Sends to | Check |
|---|---|---|---|---|
| 2 | Amina Nakato | +256 772 481 630 | +256772481630 | Valid |
| 3 | Brian Mwangi | 0701 554 210 | +256701554210 | Valid |
| 4 | Grace Nansubuga | +256701100204 | +256701100204 | Valid |
| 5 | Joseph Kato | +256 772 481 630 | +256772481630 | Duplicate |
| 6 | Sarah Akello | ask at counter | — | Invalid |
| 7 | Daniel Okello | +256 752 908 113 | +256752908113 | Valid |
| 8 | Lydia Namara | +256 772 100 208 | +256772100208 | Valid |
Local numbers are completed with +256, duplicates are merged and anything that isn’t a phone number is set aside. Your file never leaves this page.
For developers
Run the same endpoint against delivery, provider rejection and an empty wallet. Start with a test key, then switch to a scoped live key.
POST /api/v1/messagescurl -i "$SAVARA_HOST/api/v1/messages" \
-H "Authorization: Bearer $SAVARA_TEST_KEY" \
-H "Idempotency-Key: demo-1842-delivered" \
-H "Content-Type: application/json" \
-d '{
"channel": "SMS",
"to": "+256770123456",
"body": "Order 1842 is ready for pickup.",
"scenario": "delivered"
}'Guides for the stack you already use
Delivery logs
Filter by channel, open any message to see its attempt timeline, and match it to the webhook your server received.
| Time | Channel | Recipient | Status | Charge |
|---|---|---|---|---|
| 10:42:07 | +256 770 ••• 456 | delivered | $0.0280 | |
| 10:42:05 | SMS | +256 701 ••• 210 | delivered | $0.0392 |
| 10:41:58 | amina@••••.com | sent | $0.0011 | |
| 10:41:51 | SMS | +254 712 ••• 091 | failed | $0.0000 |
| 10:41:44 | +256 752 ••• 113 | read | $0.0280 | |
| 10:41:30 | SMS | +256 772 ••• 630 | sending | $0.0392 |
{ "type": "message.status",
"status": "read",
"channel": "WhatsApp" }Who it’s for
Customers who need the update, developers who send it and the team that answers when someone replies.
Mobile money
Fund your prepaid wallet with mobile money. You see the exact amount before you approve, and credit is ready as soon as the payment is verified.
Add funds
Choose an amount in the console.
Pay UGX 185,000 to SavaraFlow?
Checkout shows the UGX amount. Approve it on your phone.
Payment received
$198.50 $50.00 addedThe USD wallet is credited once the payment is verified.
Use cases
How a message moves
Pick SMS, WhatsApp or email and an approved sender. Use the API or the workspace.
SavaraFlow prices the message for its destination and segments, then reserves the amount in your wallet.
The worker sends through the configured route and records every attempt.
Delivery and read receipts land in logs, webhooks and the conversation thread.
Yes. You connect your Meta business number in the console, and SavaraFlow syncs your approved templates. Replies from customers land in the shared inbox.
Yes, in Uganda. Request a branded sender ID in the workspace and it is registered with the networks. Until it is approved, messages use the shared SavaraFlow sender.
It can’t. A batch reserves its full cost before anything is sent. If the balance is short, the whole batch is declined and nothing goes out.
If a provider rejects a message before accepting it, the charge is refunded. Once a provider accepts a message, the attempt may remain billable even if delivery later fails. The console and API show the exact charge for each message.
Yes. Sandbox keys and simulations never touch your wallet. You can try delivered, rejected and low-balance outcomes before you top up.
Each contact records the channels they agreed to. API sends require consent: true, and fallback only uses channels with recorded consent.
Mobile money through a hosted checkout that shows the amount in Ugandan shillings before you approve. Credit is added to your USD wallet once the payment is verified.
No. Pay as you go from a prepaid wallet. An optional monthly platform plan is available if you want it.
Prepaid pricing
Estimate monthly usage in seconds, then get a live quote for any destination in the console.
