$5 a month per WhatsApp number, unlimited messages in and out. Chatty agents send a lot, and per-conversation pricing punishes exactly that. Here a number is a flat fee, and you only pay for bridges that are running.
Per month. Scale up or down instantly; paused bridges cost nothing.
The fee is for the WhatsApp side: a number kept online, every message delivered to your webhook, one REST call to reply. What answers is yours, on any provider, at whatever it costs you there.
Model costs are between you and your provider. We never see or meter them.
Not a developer? Use it from Make, n8n or Zapier →
One plan. Every feature on every bridge, from the first free one to the fiftieth.
Limits are per API key and reset every 60 seconds. Going over returns HTTP 429 with a Retry-After header, so a client can back off cleanly.
| API, general | 120 req / min |
| API, proxy (send, media, contacts…) | 120 req / min |
| API, provision | 10 req / min |
| Global, per IP | 300 req / min |
| Bridges per account | 10 by defaultEmail us to raise it |
You are building on a linked device, not Meta’s official API. That is what makes it cheap and template-free. It also means you should know these three things before you build.
disconnected event the moment it happens. Re-scan the QR and the same bridge is back in about a minute, same key, same webhooks. How recovery works →Stripe takes your card when you connect your first number, with $0 due that day. The first charge of $5 per bridge per month happens on day 8, when the trial ends. Cancel the bridge before then and nothing is charged. After that, cancelling refunds the unused days.
A bridge you provisioned that is running. Paused or suspended bridges are not billed. You can cancel a bridge at any time and receive an automatic prorated refund for the unused portion of the month.
No. Send and receive as many messages as you need. The flat $5/bridge/month covers everything.
Yes. Each bridge is one WhatsApp number. Add as many as you need - billing scales linearly at $5 each.
Cancel a bridge mid-month and we immediately refund the unused days to your card. No support ticket, no waiting period. It shows up within a few business days depending on your bank. Refunds under $0.50 are skipped.
Your webhook gets a disconnected event the moment it happens, so your app knows immediately instead of finding out from users. The dashboard shows the pairing QR again - scan it and the same bridge is back, usually in under a minute, with the same API key, endpoints, and webhook config. Nothing to rebuild. While it’s down, API sends return an error instead of silently dropping, and inbound messages still land on the phone as normal since the bridge is a linked device.
Honest answer: WABridges connects to WhatsApp as a linked device - the same multi-device protocol WhatsApp Web uses - not Meta’s official Business API. WhatsApp may restrict numbers that behave like spammers, regardless of how they connect. Message people who expect to hear from you, don’t cold-blast marketing lists, and use a dedicated number rather than your personal one. Used that way, linked-device automation is low risk - but it’s never zero, and you should know that before you build on it.
Cancel the bridge and the prorated refund for your unused days is automatic, like any other cancellation. Pair a new number to a fresh bridge in under a minute. We never charge for a bridge you’re not running.