WhatsApp Business API guides for developers
The questions developers ask before and while they integrate WhatsApp, answered plainly, then quickstarts for Next.js, Python, Laravel and n8n.
Guides
- How to add WhatsApp to your SaaSThe five steps to let your SaaS send and receive WhatsApp messages on your customers' own numbers, through Meta's official Cloud API.
- Official vs unofficial WhatsApp API: what changesThe official WhatsApp Cloud API and unofficial QR-code APIs compared: how each connects a number, what each costs, and the risk of losing the number.
- The WhatsApp 24-hour window, explained for developersWhat the WhatsApp customer service window allows, what it forbids, what reopens it, and how to read it from your code before each send.
- Meta Tech Provider vs Solution Partner: who does whatThe two kinds of WhatsApp partner at Meta, what each may do, who pays Meta in each case, and which one a software publisher needs.
- WhatsApp API pricing: what Meta charges, explainedHow Meta bills the WhatsApp Business API: per message, by category and by recipient country. What is free, what is not, and who receives the invoice.
- WhatsApp Business API glossary for developersWABA, template, customer service window, messaging tier, Embedded Signup, Tech Provider, coexistence, Flow: the terms of the WhatsApp API, defined.
Quickstarts
- WhatsApp API with Next.js: receive and reply in one routeA Next.js route handler that verifies the webhook signature, reads an incoming WhatsApp message and replies, with the Nodium TypeScript SDK.
- WhatsApp API with Python: a FastAPI webhook that repliesA FastAPI app that verifies the webhook signature with HMAC-SHA256, reads an incoming WhatsApp message and replies through the Nodium REST API.
- WhatsApp API with Laravel: a signed webhook and a replyA Laravel route that verifies the webhook signature, reads an incoming WhatsApp message and replies with the HTTP client, through the Nodium REST API.
- WhatsApp API with n8n: a workflow that receives and repliesConnect WhatsApp to n8n with three standard nodes: a Webhook that receives the message, a signature check, and an HTTP Request that replies.