Connect your WhatsApp Business number through Coexistence: messages arrive at your webhook, and you send through a REST API.
Business plan: US$ 29 per month, with unlimited numbers
No card required.
A complete WhatsApp gateway for your business systems.
Receive WhatsApp messages in real-time at your webhook URL. We handle Meta's webhook complexity so you don't have to.
Send text, template, and media messages with a simple API call. Authenticate with API keys, no OAuth dance required.
Connect your WhatsApp Business number in minutes with Meta's official Embedded Signup flow. No manual token handling.
Failed webhook deliveries are automatically retried with exponential backoff. Never miss an inbound message.
AES-256 encryption of tokens and message content, JWT authentication, API key hashing, webhook signature validation, and access scoped to each organization.
Monitor message delivery, webhook health, and API usage. Manage templates, API keys, and webhook configuration from one place.
To keep a number in the WhatsApp Business app (Coexistence) or connect your customers' numbers, Meta requires you to be a Tech Provider or Solution Partner, which takes Business Verification and App Review. ZapClaw answers Chatwoot in the same dialect Meta does, so the channel connects with one env var and one API call per number, no code changes on your side. Your customers connect through our Embedded Signup. You keep your Chatwoot install.
{ object, entry[] } shape, signed with X-Hub-Signature-256. Chatwoot's existing handler reads it without a single patch.
POST /v25.0/{phone_id}/messages with a Bearer token. Mirrors the surface Chatwoot's WhatsappCloudService already calls.
Get up and running in three simple steps.
Sign up and connect your WhatsApp Business number via Embedded Signup. ZapClaw handles the OAuth token exchange automatically.
Set your webhook URL to receive inbound messages. Generate an API key to send outbound messages from your system.
Inbound messages flow to your webhook. Outbound messages go through our REST API. ZapClaw bridges the gap.
Monely, a personal finance app from the company behind ZapClaw, has run its WhatsApp numbers on ZapClaw since July 2026. Messages come in on its webhook, and replies go out through the REST API with idempotency keys.
Common questions about ZapClaw.
ZapClaw, a Meta Tech Provider, is a WhatsApp message gateway that connects your business phone number to the official Meta Cloud API. It receives inbound messages and forwards them to your webhook URL, and lets you send outbound messages via a REST API.
ZapClaw connects your number through Meta's official API, not through an unofficial library that imitates WhatsApp Web, the kind of connection that goes against WhatsApp's terms and puts numbers at risk. WhatsApp's messaging policies still apply, as they do to any business. How the two kinds of connection compare.
Yes. ZapClaw uses Meta's official WhatsApp Cloud API. During the connection, Meta's own window links your WhatsApp Business app number to a WhatsApp Business Account (WABA) in your Meta business portfolio, and creates that account if you don't have one yet. If Meta asks for a phone number first, type or pick the number of your WhatsApp Business app and go on only if Meta then shows that app's profile. If it shows two options, choose Connect a WhatsApp Business app; the other one, Create a WhatsApp Business account, is for brand new numbers and does not work with ZapClaw. Stop if Meta sends a code by text message or phone call.
Coexistence connects a number that already runs on the WhatsApp Business app (the business app, not regular WhatsApp). You keep using the app on your phone while ZapClaw handles API messages in parallel.
When someone sends a message to your WhatsApp number, Meta delivers it to ZapClaw via webhook. ZapClaw then forwards the message payload to your configured webhook URL in real-time. If your endpoint is down, we make up to 3 delivery attempts in total: right away, 30 seconds later, and 2 minutes after that.
Generate an API key in your dashboard and use our REST API. Send text messages, template messages, or media (images, videos, documents) with a simple POST request using your API key in the X-API-Key header.
We protect it in layers: message content is encrypted at rest with AES-256-GCM, access tokens are encrypted under a separate key, API keys are stored as SHA-256 hashes, all communication uses HTTPS, Meta webhook signatures are checked, and the dashboard and the API read only the data of the organization a request belongs to. No system is 100% secure; our Security page describes the measures.
No CNPJ required to connect. Coexistence works for autonomous professionals, MEIs, and informal entrepreneurs. To connect you need: (1) a personal Facebook account with 2FA enabled, (2) the WhatsApp Business app on the number, in regular use (Meta may refuse numbers with little recent activity; in practice about 7 days of use has been enough), (3) the app updated to version 2.24.17 or newer, (4) the number not connected to any other provider, and (5) a computer to run the connection, with your phone at hand to confirm it in the WhatsApp Business app. A CNPJ only matters for Meta's business verification: what changes without a CNPJ. All the requirements.
Meta refuses Coexistence for numbers with too little recent activity on the WhatsApp Business app. Meta doesn't publish the threshold; in practice about 7 days of real use has been enough. This is a Meta anti-abuse check, not a ZapClaw limitation. Keep using the number normally (replying to a few contacts each day) and try again in a few days. Don't delete and re-register the number: that starts the count over. More on this.
The number is still linked to the provider you used before, sometimes even after you cancelled there. In the WhatsApp Business app, open Settings > Account > Business Platform, tap Disconnect, wait 15 minutes and connect again. If Meta still refuses it: log the number into regular WhatsApp, move it back to WhatsApp Business, wait 30 minutes and retry. ZapClaw shows this workaround automatically when it detects this error. More on this.
Yes. Native and Chatwoot are two independent destinations, each with its own URL and on/off switch, and both can be active on the same number at once. A common setup is Chatwoot for human support plus your own endpoint driving automation; every inbound message is delivered to each, in the shape that destination expects. Turning one on never disables the other. More on this.
No. Stop and close Meta's window. That request only appears on the path for brand new numbers, which ZapClaw doesn't use, and deleting the account takes the number out of the WhatsApp Business app, which is exactly what Coexistence needs. Start again: if Meta asks for a phone number first, type or pick your WhatsApp Business app number and go on only if Meta then shows that app's profile; if it shows two options, choose Connect a WhatsApp Business app. Stop if Meta sends a code by text message or phone call. ZapClaw never requires deleting anything. More on this.
Not from the phone's browser: the connection runs on a computer, and the dashboard tells you so if you open it on a phone. Your phone still takes part: during the connection you confirm it in the WhatsApp Business app, by scanning the QR code shown on the computer or pasting the code it shows.
That is Meta protecting your business portfolio, and its Next button keeps spinning until the check is cleared. On the same computer and browser, open business.facebook.com, enter the portfolio you are connecting and complete the verification Meta asks for (usually a code). Then reload ZapClaw and connect again. Two-factor authentication must also be on in your Facebook account. More on this.
Meta's official Coexistence requirements list no country restriction, and the final word is Meta's own check during the connection. On the phone you need the WhatsApp Business app, on Android or iPhone, version 2.24.17 or newer. Linked devices are disconnected when you connect and can be linked again, except WhatsApp for Windows and WearOS, which Meta does not support with Coexistence. Keep opening the app on your main phone: Meta disconnects the number after about 14 days without it. Connecting from Germany or the EU.
Meta offers no separate eligibility check. It checks the number inside its own connection window, before the connection is completed: if the number isn't eligible, the window stops with an error, nothing is authorized, ZapClaw receives no access and the attempt costs nothing.
No. During the connection the WhatsApp Business app asks whether to share your chat history. If you decline, nothing is imported. If you accept, Meta sends up to 180 days of history, which ZapClaw keeps for no longer than the period your organization chooses, counted from the import: 90 days by default, configurable to 30, 7 or 0 (no content kept). With 0, no history is imported. The app's contact list is always synced.
Never. ZapClaw only sends a message when your system calls the send API or you send it from the dashboard. Receive-only use is fully supported: messages reach your webhook, and your team keeps replying from the WhatsApp Business app. How to set it up.