How do webhooks work?

You give us a URL and tick which of the 74 events you want. When one happens we POST a signed JSON payload to you within seconds — no polling. Failures are retried with backoff, and every attempt is in a log you can read, including the response we got back.

Can I limit what an API key can do?

Yes. Keys are scoped by route and by channel, and an empty scope means all — so you can issue a key that may only read contacts on one WhatsApp number. A route that has not been mapped to a scope fails closed rather than open, which is the safe direction to be wrong in.

Are there rate limits?

Per plan, and they are documented and returned in the response headers so you can back off politely rather than guess. Bulk sends are queued rather than executed inline, so a hundred-thousand-message job returns immediately instead of holding a connection open for an hour.

Is there a sandbox and sample code?

There is a sandbox, a Postman collection, and working examples in the common languages on the docs site. Most teams get from creating a key to a successful first call inside five minutes.

How it works

API & Webhooks

WhatsApp Business API and webhooks for developers

Everything the app does, your software can do too.

Start free — forever Book a walkthrough

38 live eventsA documented APIEvery call logged

MotherBot — Webhooks & API

Configure Webhook

Endpoint URL

https://api.yourapp.com/webhook

Method

POST

GET

Test Webhook

Save

What changes

The difference, in numbers

Typical results from accounts running this. Yours will differ — these are the shape of it.

0
Events pushed to you in real time: PollingPushed
How you learn something happened: 5 min
From key to first successful call: 100%
Of the app's surface, exposed

See it happen

Three businesses, three real conversations

Pick the one closest to yours. The chat plays on the left; what MotherBot did is on the right.

SYSystem → Systemonline

POST /v1/messages — order confirmation

A marketplaceWhat MotherBot did, meanwhile

Sent from their backend, template + variables01

The honest comparison

The same week, run twice

Right now

Polling an endpoint every minute to see if anything changed
A vendor API that covers half of what the UI does
Keys with full access, because scopes were not offered
A failed call that disappears with no way to see why

A week of integration work, and a fragile result

With MotherBot

Thirty-eight events pushed the moment they happen
Contacts, messages, templates, broadcasts, flows, analytics
Keys scoped to routes and channels — empty means all
Every call logged, signed, and retried on your behalf

A morning, and something you can put in production

Setting it up

Six steps, and you're running

It plays on its own. Tap any step to hold it — the dashboard above follows along.

MotherBot — Webhooks & API

Configure Webhook

Endpoint URL

https://api.yourapp.com/webhook

Method

POST

GET

Test Webhook

Save

1/6

What's included

Everything in the box

All of it on every plan. The plan sets your volume, not what you can do.

Thirty-eight events

Message, template, order, deal, payment and flow changes.

Signed, so you can verify

Every payload carries a signature you check before trusting.

Retried without you asking

Backed off and retried, with the full attempt log kept.

Keys with real scopes

Per route and per channel. An unmapped route fails closed.

The whole surface

Contacts, messages, templates, broadcasts, flows, analytics.

Bulk sends are queued

A hundred thousand messages, without holding a connection open.

Postman collection
Per-plan rate limits
Cursor paging
Sandbox to test in
Secrets masked in logs
Chrome extension tokens
Spreadsheet extension tokens
Zapier app

Who runs this

Six industries, six real jobs

Not a list of industries — what each one actually does with it, and what they get back.

Marketplaces

Order events pushed both ways between their platform and chat.

Buyers updated without a single manual message.

Hospitals

A nightly job posts tomorrow's appointment reminders in bulk.

Legacy software gains WhatsApp without being rewritten.

Analytics teams

Contacts and broadcast results pulled into the warehouse.

WhatsApp joined to ad spend on one customer id.

Agencies

Zapier for the client requests that arrive on a Friday.

Delivered same day, with no engineering ticket.

Fintech

Higher delivery than SMS, at a lower price.

Logistics

Scan events posted as they happen, straight into the thread.

Tracking that is genuinely live, not hourly.

See the full playbook for your industry

It doesn't work alone

What API & Webhooks plugs into

Every part of MotherBot works off the same contacts, the same inbox and the same numbers.

API & Webhooks

IntegrationsBuilt on this same public surface BroadcastsTrigger a send from your own code TemplatesCreate and submit them programmatically AnalyticsPull the numbers into your own tools ContactsRead and write the customer record AI ChatbotsCall your API mid-conversation

Questions

The ones people actually ask

Everything the app does. The v1 REST API covers contacts, messages of every type, templates, broadcasts, flows, chatbots and analytics, across all ten channels — not WhatsApp alone. If you can do it on a screen here, there is an endpoint for it.

Keep going

The other eleven

AI Chatbots Broadcasts Live Chat Contacts Analytics Templates Integrations WhatsApp Flows Payments Team & Roles Website Button

Get started

Have this running today

Free forever, not a trial. A real person will set it up with you.

Start free See pricing

No card neededKeep your numberLive the same day