Developer platform
Built to the standard you expect from a payments API.
A versioned REST API with scoped keys, idempotent writes and signed webhooks, documented from the same spec the server runs on.
# send a template with a document
POST /v1/messages
Idempotency-Key: report-88213
{ "to": "919876543210",
"template": {
"name": "report_ready",
"params": { "patient_name": "Sunita" },
"header": { "document": "https://…" } } }
# 201 Created
{ "id": "msg_01J8…", "status": "queued",
"cost": { "category": "utility", "inr": 0.115 } }Webhook deliveriescrm.example.in
- message.status_changed · read200 · 84 ms
- contact.stage_changed · Booked200 · 61 ms
- message.received503 · retry 3 of 5 in 4 min
- flow.session_completed · Appointment FAQ200 · 122 ms
HMAC-SHA256 signed, timestampedRedeliver
What it is
The developer platform is a versioned REST API and webhook system on top of the WhatsApp Business Platform, so a business's own software can send template and session messages, manage contacts and segments, launch campaigns, enrol people in journeys, post conversions and events, and receive signed webhooks when a message arrives, a status changes or a contact opts out. Keys are scoped and rate-limited, writes take idempotency keys, the reference is generated from the live OpenAPI spec, and every webhook delivery is logged with a one-click redeliver.
What it does
Every line below is in the product today. The ones marked only here were not found in WATI’s, AiSensy’s or Interakt’s public documentation on 20/09/2026.
REST API at /v1
Messages, templates, contacts, segments, campaign triggers, media, journeys, conversions, events. Idempotency keys, cursor pagination, one error envelope.
Scoped keys
Per-key scopes, rate limits with headers, test mode, an IP allowlist, revoke, last-used visibility.
Webhooks with a debuggerOnly here
HMAC-signed, retried with backoff. Every delivery attempt, payload and response kept, redeliver in one click.
Docs from the spec
A public reference rendered from the live OpenAPI spec, with an in-dashboard reference and curl examples.
Events in, journeys out
Post "order shipped" to the events endpoint and a journey starts or ends. Conversions posted the same way land on the campaign that earned them.
Zapier, Make, n8n, Pabbly, Sheets
REST hooks for the automation tools you already use, and Google Sheets in and out for everyone else.
Questions about developer platform
Is there a WhatsApp API for developers?
Meta's WhatsApp Cloud API is the underlying platform. This product's REST API sits on top of it and adds what Meta does not: contacts and segments, campaigns, journeys, conversions, events, scoped keys, signed webhooks with a delivery log, and one consistent error envelope.
How do webhooks work?
Subscribe an HTTPS endpoint to any of eleven events, such as message received, status changed, contact opted out or form submitted. Each delivery is signed with HMAC-SHA256 and a timestamp, retried with exponential backoff up to five times, and logged with its payload and your response code so it can be redelivered by hand.
Can I send OTPs over WhatsApp?
Yes. Authentication templates with a one-tap or copy-code button are sent through the messages endpoint and billed at Meta's authentication rate.
Is there a sandbox?
Test-mode keys accept every request and return realistic responses without sending anything to Meta, so an integration can be built and tested before it touches a real number.
Talk to us.
In a forty-minute call we go through what you send today, what it costs you, and what a flagged number would cost you. Then we set up a workspace on your own Meta app and build the first campaign with you.