Build your product on top of WABridges. Provision one bridge per customer with a single API call, point each number at its own bot logic, and charge whatever you want on top. You own the customer, we run the WhatsApp layer.
Every SaaS eventually gets the same request: "Can my customers talk to this over WhatsApp?" Building that yourself means the WhatsApp Business API, template approvals, per-message fees, and a multi-tenant connection layer you have to operate forever.
WABridges is that layer, rented by the bridge. Provision one bridge per customer with a single API call, let each of them pair their own number, and route every inbound message, tagged with the customer it belongs to, into your own bot. You resell it under your brand at whatever price you like. We bill you a flat $5/month per active bridge; the markup is yours.
We keep the number online and hand you every event. You write the part in the middle.
When a customer signs up in your app, POST to /api/instances with a customer_ref that identifies them (e.g. "cust_123"). You get back a bridge they fully control, one API call, under 60 seconds.
Surface the pairing QR or link-code from the bridge inside your own UI. Your customer scans it with their WhatsApp number, personal, VoIP, or business. Their number, your platform.
Set each bridge's webhook to your backend. Every inbound message arrives tagged with its customer_ref, so you know whose bot should answer, your AI assistant, their FAQ flow, or whatever you built.
Your wholesale cost is a flat $5/month per active bridge. Charge your customers monthly, per-seat, or usage-based, you set retail pricing and own the invoice. Cancel a bridge and you get a prorated refund.
Every loop below is the one above with your own logic in the middle.
Copy this prompt, paste it into any AI assistant, get working code in your language.
I'm building a multi-tenant SaaS where each of my customers gets their own WhatsApp bot, powered by WABridges. WABridges gives me a REST API to provision one bridge (one WhatsApp number) per customer. My stack: [Node.js / Express + Postgres, update this to yours] My setup: - WA_API_KEY: my WABridges API key (one key for my whole account) - Each of my customers has an id in my "tenants" table I need three pieces: 1. provisionBridge(tenantId): calls POST /api/instances with customer_ref set to my tenant id and webhook_url pointing at my backend. Store the returned bridge id on the tenant record. 2. A POST /webhook endpoint that receives inbound WhatsApp messages. The payload includes the customer_ref so I know which tenant the message belongs to. Look up that tenant, run their bot logic (for now, a placeholder runBot(tenant, message) function), and reply via the send API on that tenant's bridge. 3. deprovisionBridge(tenantId): deletes the bridge when a tenant cancels, so I stop being billed for it. Please read the WABridges API docs before writing any code: https://wabridges.com/llms-full.txt Keep tenant isolation strict: one tenant must never receive or send on another tenant's bridge. Show runBot() as a clearly separated stub I can later swap for an LLM call.
What you get on the WhatsApp side, whatever you build on yours.
Other guides that build on the loop you just read.
Choosing a provider? See how WABridges compares to Twilio, 360dialog, and other WhatsApp API providers.