Multiple webhooks for WhatsApp

The WhatsApp Business API (WABA) lets you register only one webhook URL per phone number. As soon as more than one system needs inbound events — say a CRM, an analytics pipeline, and your own backend — that single slot becomes a bottleneck, and you end up building your own fan-out service.

get.chat solves this with webhook (de)multiplexing: it receives the single WABA webhook and forwards every event to multiple, independently configured per-user webhooks that you control.

                         ┌────────────► your backend
WhatsApp ──► get.chat ───┼────────────► your CRM
 (1 WABA webhook)        └────────────► analytics / automation
                          (many per-user webhooks)

Manage your webhooks

Configure webhooks through the Integration API:

GET  /api/v1/webhooks/waba/            # list your webhooks
GET  /api/v1/webhooks/waba/{id}/       # inspect one
PUT  /api/v1/webhooks/waba/{id}/       # update its target URL
GET  /api/v1/webhooks/waba/{id}/test/  # send a test event to it

You can also manage them from the Admin Panel → WABA Webhooks section if you prefer a UI.

What you receive

Each configured endpoint receives inbound messages and message-status updates as JSON POST requests, so every consumer reacts to the same events in real time without competing for the single WABA slot.

See the full event payloads in the WhatsApp Integration API reference, and the Quickstart for an end-to-end send/receive walkthrough.