WhatsApp Business API with direct Meta-to-your-server webhooks
Dualhook helps teams use the WhatsApp Business API while keeping a cleaner architecture around Cloud API and the WhatsApp Business App. Message webhooks go directly from Meta to your endpoint, so Dualhook stays out of the message path and out of message storage.
Dualhook connects teams to the WhatsApp Business API with direct Meta-to-server webhook routing, zero message storage, and optional coexistence with the WhatsApp Business App.
What is the WhatsApp Business API and where does Dualhook fit?
Teams still use WhatsApp Business API as the umbrella term, while Meta documentation often talks about Cloud API or the WhatsApp Business Platform. For most implementation work, that is the same stack: API-based sending, template management, webhook delivery, and business account configuration.
Dualhook sits around that stack rather than in the message path. It helps teams keep the Business App through coexistence, send message webhooks straight from Meta to their own backend, and manage setup and operations without adding another inbox layer.
If you are preparing for Meta's BSUID and username rollout, use the Meta BSUID transition guide for the webhook field changes, contact book behavior, and migration timeline.
Why do teams choose Dualhook for WhatsApp Business API?
- Keep the Business App available through WhatsApp Coexistence.
- Route message webhooks directly to your own backend.
- Avoid storing messages in another vendor's shared inbox.
- Get setup, monitoring, and template tooling in one place.
Direct routing vs BSP and shared inbox architecture
Many providers in the WhatsApp Business API market act like a middle layer. They proxy inbound and outbound traffic so they can power inbox, CRM, and reporting features. That can be useful for some teams, but it also means more infrastructure between Meta and your system.
Dualhook takes the opposite position. It uses WhatsApp Webhook Override so message events go directly from Meta to your endpoint. Dualhook focuses on setup, coexistence support, and operational tooling rather than becoming the place where your messages live.
How much does Dualhook cost?
Dualhook charges a flat monthly subscription for the product layer. Meta bills message usage separately under the WhatsApp Business Platform. That gives teams a clearer split between infrastructure costs and the tooling needed to keep coexistence and routing healthy.
Frequently asked questions about WhatsApp Business API
Is WhatsApp Business API the same thing as Cloud API?
In most searches, yes. People still search for WhatsApp Business API, while Meta's current product naming focuses on WhatsApp Business Platform and Cloud API.
Do I need a BSP to use WhatsApp Business API?
No. Teams can work directly with Meta's Cloud API. Dualhook helps with coexistence, direct webhook routing, and operations without becoming a message proxy.
Can I keep the WhatsApp Business App when I use WhatsApp Business API?
Yes, if the number is eligible for WhatsApp Coexistence. Dualhook focuses on that app-plus-API setup.
Where do message webhooks go in a Dualhook setup?
Meta sends message webhooks directly to your server through Webhook Override. Dualhook does not proxy or store the message content.
Supporting guides
Use these docs and comparisons to go deeper on the WhatsApp Business API stack.
WABA integration guide
Follow the end-to-end account integration path for WhatsApp Business Accounts and Cloud API setup.
WhatsApp webhook setup
See how Dualhook configures Webhook Override so message-path events go directly from Meta to your server.
Meta BSUID transition guide
Understand user_id, usernames, contact book behavior, and the March 31, 2026 webhook changes.
Dualhook vs traditional BSPs
Compare direct Cloud API routing with providers that proxy messages through their own infrastructure.
Want a cleaner WhatsApp Business API architecture?
Start with Dualhook if you want Cloud API, coexistence, and direct webhooks without adding a message proxy to the middle of the stack.