The WhatsApp API
your code can actually use
Scan one QR code and send WhatsApp messages from your app over plain HTTP. No Business API application, no template approvals, no waiting weeks for Meta.
Free tier to try it · No card required · Cancel anytime
curl -X POST \
https://api.mocode.co.tz/v1/whatsapp/sessions/$SESSION/messages/send-text \
-H "Authorization: Bearer $MOCODE_KEY" \
-H "Content-Type: application/json" \
-d '{"to":"255700000000","message":"Your order is ready 🎉"}'That's the whole integration. No SDK required.
What people build with it
Messages people actually read — WhatsApp gets opened, email doesn't.
One-time passcodes
Deliver login and confirmation codes where people already are, without SMS gateway fees.
Order updates
Confirmations, dispatch notices and delivery alerts sent the moment your system knows.
Reminders
Appointments, renewals and payment due dates — scheduled from the software you already run.
Two-way support
Webhooks push incoming messages to your app, so replies land in the tools your team uses.
Everything you need, nothing you don't
A complete messaging platform — not just a wrapper around a library.
Multiple numbers
Run separate numbers for sales, support and deliveries from one workspace, each with its own session.
Every message type
Text, images, video, audio, documents, locations, contacts, stickers, reactions and replies.
Signed webhooks
Incoming messages and delivery receipts pushed to your server, HMAC-signed and retried on failure.
Honest REST API
Predictable JSON, stable error codes, and an OpenAPI spec generated from the API itself.
Usage you can see
Every request logged with status and timing. Know exactly what you used before the invoice arrives.
Keys you control
Scope keys down to single endpoints or sessions, restrict them by IP, and roll them instantly.
Live in three steps
Most people send their first message within five minutes of signing up.
- 1
Connect your number
Create a session and scan the QR code with WhatsApp on your phone — the same flow as WhatsApp Web.
- 2
Create an API key
Generate a key scoped to what your application actually needs, and store it in your environment.
- 3
Send messages
One HTTP POST and your message is on its way. Watch it land in your request logs in real time.
Flat monthly pricing
You pay for the plan, not per conversation. No surprise invoice after a busy month.
Need more, or an invoice in TZS? See full pricing.
Why not the official Business API?
It's the right choice for some. Here's the honest comparison.
| Mocode Connect | Meta Business API | |
|---|---|---|
| Setup time | About 5 minutes | Days to weeks of review |
| Business verification | Not required | Required |
| Message templates | Send any message | Pre-approved templates only |
| Pricing | Flat monthly fee | Per-conversation billing |
| Group messaging | Supported | Not supported |
| Green tick badge | Not available | Available |
| Best for | SMEs, startups, internal tools | Large enterprises at scale |
Mocode Connect links a regular WhatsApp account the same way WhatsApp Web does. It is not affiliated with or endorsed by WhatsApp or Meta. Use it in line with WhatsApp's terms — send to people who expect to hear from you.
Questions worth asking first
Straight answers, including where this isn't the right tool.
Will my number get banned?
It can be, if you use it the way spam does. WhatsApp acts on how a number behaves, not on which software sends the messages: unsolicited bulk sends to people who never asked, high volumes from a brand-new number, and above all being reported. Message people who expect to hear from you, warm a new number up gradually, and keep opt-outs working, and this behaves like any ordinary WhatsApp account. We cannot indemnify you against a ban, and anyone who promises otherwise is guessing.
How is this different from the official Business API?
This links a normal WhatsApp account the way WhatsApp Web does, so there is no business verification, no template approval and no per-conversation billing. The trade-offs are real: no green tick, and no contractual guarantee from Meta. If you send at very large scale or need the verified badge, the official API is the better fit.
What happens if my phone goes offline?
The session stays linked, exactly like WhatsApp Web. Your phone needs to come online periodically for WhatsApp to keep the link alive, so treat the connected phone as part of the system: keep it charged, online, and do not log the device out of linked devices.
Can I use more than one number?
Yes. Each number is its own session, and the plans differ mainly in how many you can run at once. Teams typically separate sales, support and delivery notifications so one number going quiet does not take everything down.
Do you read or store my messages?
Message content passes through the API in order to deliver it, and request logs record metadata — endpoint, status, timing — so you can debug and see your usage. Logs expire automatically. We do not sell data or use your message content for anything other than running the service.
How do I pay from Tanzania?
Payments run through DPO Pay, which accepts Tanzanian mobile money and cards. Plans are listed in USD and settled in TZS at checkout. Card details are entered on the payment provider’s own page and never touch our servers.
What if I need help getting started?
The dashboard has an API tester so you can send a message without writing code, and the docs include working examples in several languages. If you are stuck, email us — a real person answers.
Send your first message today
Start on the free plan. Upgrade when your volume needs it.