Webhook Override
How Dualhook uses Meta's Webhook Override to route message webhooks directly to your server.
What Is Webhook Override?
Webhook Override is a Meta feature that lets an app redirect specific webhook fields to a custom URL. Instead of all webhooks arriving at a single app-level endpoint, you can route individual fields to different destinations using the callback_override_uri parameter.
How Dualhook Uses Webhook Override
When you configure a connection, Dualhook calls Meta's subscribed_apps endpoint with your webhook URL as the callback_override_uri. Dualhook subscribes to the messages and history fields with this override. This means all message webhooks are delivered directly from Meta to your server.
Management events — template status updates, quality rating changes, and account alerts — remain on Dualhook's app-level webhook. This separation is what makes Dualhook's privacy-first architecture possible.
Privacy-First Architecture
Because messages route directly from Meta to your endpoint, Dualhook never sees, proxies, or stores message content. Your webhook_verify_token is sent only in the override payload to Meta and is used by Meta to verify your endpoint. Dualhook stores it solely for configuration purposes.
What Stays on Dualhook?
- Template status updates (approved, rejected, paused)
- Phone number quality rating changes
- Account review and policy enforcement alerts
- Business verification status changes
Only operational metadata from these management events is logged. No message content is ever stored.