Guides

Working recipes. Copy, paste, ship.

Every guide is a complete loop you can drop into your stack: what to provision, what arrives on the webhook, what to send back. Underneath, they are all the same three calls.

AI agents3 Notifications and flows6 No code3 Platforms and multi-tenant6 Just for fun1

AI agents

3 guides

A model behind a real number. The loops the product was built for.

Support customers where they already are. Your customers live on WhatsApp: let them message you there. Guide Build a WhatsApp AI chatbot in an afternoon. Receive every inbound message as a webhook. Reply via REST API. Guide Connect WhatsApp to Claude. Wire a real WhatsApp number to Anthropic's Claude models. Guide

Notifications and flows

6 guides

Send from your backend, verify codes, remind, route leads. No model required.

Emails get ignored. WhatsApp gets read. Order confirmations, server alerts, deploy notifications, payment failures, send them where people actually look. Guide Verification codes that actually arrive. SMS OTPs get lost to carrier filtering and routing gaps, and cost you per message. Guide "Where's my order?" Answered before it's a ticket. Your most common support question, resolved without an agent: customers text your WhatsApp number, your backend looks up the… Guide WhatsApp appointment reminders that cut no-shows. Send automated appointment reminders over WhatsApp. Guide Every WhatsApp lead, straight into your CRM. When a prospect messages your WhatsApp number, your backend captures their number, tags them, and logs the conversation in your… Guide Alerts your on-call team actually sees. When production breaks, the alert has to land where your team actually looks. Guide

No code

3 guides

Make, n8n and Zapier through their built-in HTTP and webhook steps.

WhatsApp in your Make scenarios. No code required. Make's built-in HTTP and webhook modules talk to WABridges directly, nothing to install, nothing to program. Guide Your n8n workflows, now on WhatsApp. Import a ready-made workflow, add two credentials, and send your first WhatsApp message from n8n in ten minutes, no community… Guide WhatsApp in your Zaps. No official app needed. Zapier's built-in Webhooks feature connects your Zaps to WABridges: send WhatsApp messages as an action, and catch incoming… Guide

Platforms and multi-tenant

6 guides

One API key, many customers, each with their own WhatsApp number.

Give every customer their own WhatsApp bot. Build your product on top of WABridges. Provision one bridge per customer with a single API call, point each number at its own… Guide One API key. A fleet of WhatsApp numbers. Your whole account runs on a single WABridges API key. Guide A "Connect WhatsApp" button, living inside your app. Give your customers a one-click way to link their WhatsApp number, the pairing QR rendered in your own UI, the bridge provisioned… Guide Buy at $5. Sell at whatever you want. WABridges is your wholesale cost: a flat $5/month per active WhatsApp number. What you charge on top is entirely yours. Guide One webhook. Many tenants. Never crossed. A single endpoint can serve every bridge in your fleet. Guide Provision on signup. Deprovision on churn. Let your billing system run your WhatsApp fleet. Guide

Just for fun

1 guide

Because a REST API for WhatsApp is also a toy.

Prank your friends on WhatsApp. Auto-reply as a confused AI. Fake endless typing. Reply only in pirate speak. Guide

Describe it to your AI. It has the docs.

The full API ships as one Markdown file built for LLM context. Paste it into Claude, Cursor or ChatGPT, describe the bot, and it writes the loop for your stack.

llms-full.txt

Give your assistant the APIOne file, every endpoint and webhook payload. Then: “write me a WhatsApp bot that answers questions about my docs.”

curl https://wabridges.com/llms-full.txt

Open the file

no code

Not a developer?Make, n8n and Zapier can all call the API with their standard HTTP and webhook steps. No official app needed, no servers to run.See the no-code path