WABridges is your wholesale cost: a flat $5/month per active WhatsApp number. What you charge on top is entirely yours. Package it, brand it, price it per-seat or flat, and keep the margin on every bridge you resell.
Reselling is the oldest business model there is: buy at wholesale, add value, sell at retail, keep the spread. WhatsApp connectivity is a great thing to resell because the wholesale price is flat and predictable, and the retail value to your customers, a working WhatsApp number wired into your product, is worth far more than it costs you.
Your wholesale cost on WABridges is $5/month per active bridge. That's the whole input. There are no per-message fees, no template-approval surcharges, and no minimum commitment. You decide the retail price, $19, $49, bundled into a higher tier, whatever the market bears, and the difference is your margin. When a customer churns and you delete their bridge, your cost stops immediately with a prorated refund, so your margin never goes underwater on a cancelled account.
We keep the number online and hand you every event. You write the part in the middle.
Every active bridge costs you a flat $5/month, one WhatsApp number, unlimited messages, no usage tiers. That's the only variable cost in your unit economics, so your margin math is trivial to model.
Charge what the value is worth to your customer, not what it costs you. Flat monthly, per-seat, or baked into a premium plan, a $5 input billed at $29 is a 83% gross margin per account before your other costs.
When a customer buys, POST to /api/instances with their customer_ref and start your own subscription clock. You invoice them; we invoice you. The two are completely decoupled, your pricing is never exposed to us.
When a customer cancels, delete their bridge. Your $5 charge stops with a prorated refund for the unused days, so a mid-month churn doesn't eat into the margin you already collected.
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 reselling WhatsApp bridges to my customers on top of WABridges. My wholesale cost is a flat $5/month per active bridge; I set my own retail price and keep the margin. I want a small model and the provisioning glue. My stack: [Node.js + Stripe for billing, update this to yours] My setup: - WA_API_KEY: my WABridges API key - Stripe for charging my customers at my retail price - Each customer has an id I'll use as customer_ref I need: 1. A pricing helper that takes my retail price per bridge and returns the per-account gross margin and margin %, given the $5 wholesale cost. Print a small table for retail prices of $9, $19, $29, and $49. 2. provisionOnSale(customerId): when a customer's Stripe subscription becomes active, POST /api/instances with their id as customer_ref and store the returned bridge id against the customer. 3. deprovisionOnChurn(customerId): when their subscription is cancelled, delete the bridge so my $5 cost stops and I get the prorated refund. Please read the WABridges API docs before writing any code: https://wabridges.com/llms-full.txt Keep my retail pricing entirely on my side, WABridges should only ever see the flat wholesale relationship. Comment the margin math clearly so I can tweak my prices later.
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.