Paid Plans5 min read· Updated 2026-11-18
Outbound Webhooks & HMAC
Receive real-time inbound WhatsApp webhook events at your HTTPS endpoint, choose FORWARD_AND_PROCESS vs FORWARD_ONLY mode, and verify X-OmniChat-Signature.
Webhook forwarding modes
Configure your outbound HTTPS webhookUrl and delivery mode in Settings → Developer API (/settings/developer) or via PUT /api/v1/developer/settings:
| Mode | Behavior |
|---|---|
| FORWARD_AND_PROCESS | Forwards the incoming WhatsApp event to your webhookUrl AND continues processing inside Omni Chat Stack (Shared Inbox, AI Chatbot, Workflows). |
| FORWARD_ONLY | Forwards incoming WhatsApp events straight to your webhookUrl so your own backend handles replies exclusively. |
Verifying X-OmniChat-Signature (HMAC-SHA256)
Inbound WA Event
FORWARD_AND_PROCESS or FORWARD_ONLY
HMAC-SHA256 Signer
Adds X-OmniChat-Signature: sha256=...
Your HTTPS Endpoint
Verify timing-safe digest & return 2xx
- Headers sent on every delivery: Content-Type: application/json, User-Agent: OmniChat-Webhook/1.0, and X-OmniChat-Signature: sha256=<hex_hmac_sha256>.
- Secret management: Your webhookSecret is encrypted at rest and can be rotated anytime via POST /api/v1/developer/settings/webhook-secret.
- Timeouts & resilience: Deliveries enforce a 10-second timeout. Return HTTP 2xx promptly and process heavy downstream logic asynchronously.