WhaBuzz developer docs

WhaBuzz is a WhatsApp Cloud API gateway. Meta's request and response bodies, plus tenants, API keys, signed webhooks with retries and replay, and an event log.

WhaBuzz connects your WhatsApp Business numbers to your server through Meta's Cloud API. You send Meta's own message and template bodies to api.whabuzz.com; Meta's own answers come back. Everything Meta sends about your numbers reaches your server as a signed webhook, with the full original payload attached.

We are a Meta Tech Provider. You pay Meta's rates to Meta. You pay WhaBuzz a flat monthly fee per number, never per message.

#The shape of it

your server  --POST /v1/messages-->  api.whabuzz.com  --Graph API-->  Meta
your server  <--signed webhook--     hooks.whabuzz.com <--webhook--    Meta

• Outbound. POST /v1/messages takes Meta's /messages body plus a from field. WhaBuzz adds nothing, removes nothing, and reorders nothing. The response is Meta's response.
• Inbound. Messages, delivery statuses, template reviews, quality changes and account notices are delivered to your endpoints as events. At-least-once, signed, retried for 24 hours, replayable.
• Errors. Either WhaBuzz stopped the request ("source":"whabuzz") or Meta answered with an error, passed through untouched ("source":"meta"). See Errors.

WhaBuzz makes no decisions for you. It does not look at template categories, the 24-hour window, opt-outs or message content. Meta decides, and you see Meta's decision.

#Start here

1. Getting started: sign up, connect a number, send a template, receive the first event.
2. Authentication: API keys, the Authorization header, platform keys.
3. Webhooks: signing, the verify ping, retries and replay.
4. Event catalogue: every payload, with the real fixture and the envelope you receive.
5. API reference: every endpoint with request, response and error examples.

#Pick your path

• One business, one integration. Sign up, connect your number in the console, create a key, send. Getting started.
• A platform serving many businesses. Use an app key, create tenants, and send your customers a hosted Embedded Signup link.
• Moving from Plivo or WATI. Migration guide.

#For agents and scripts

Every page here is also served as Markdown: add .md to the path, or send Accept: text/markdown. The whole site is in one file at /llms-full.txt, with an index at /llms.txt. The OpenAPI 3.1 contract is at /openapi.yaml and /openapi.json.

This page as Markdown: /index.md. All docs in one file: /llms-full.txt.