WhatsApp Business API Explained
Wovara Team · · 9 min read
"WhatsApp Business API" is the name almost everyone still uses, even though Meta renamed it the WhatsApp Business Platform a while back. Whatever you call it, it's the infrastructure that lets a business send and receive WhatsApp messages programmatically, at a scale and with a set of team features the consumer app was never built for — and understanding what it actually is (and isn't) clears up a lot of confusion about how tools like Wovara relate to it.
It's Meta's infrastructure, not a product you use directly
The WhatsApp Business Platform is a set of APIs Meta operates — most commonly accessed today via the Cloud API, which Meta hosts directly (there used to be a self-hosted On-Premises version; Meta has been retiring it in favour of Cloud API). It has no user interface of its own. A business doesn't log into "the API" and start chatting — it needs a layer on top, built by Meta itself or by a third party (often called a Business Solution Provider, or BSP), that gives people an actual inbox, template manager, and so on to work from. Wovara is that layer: it connects to the Cloud API on a business's behalf and gives the team a usable product on top of it.
How a business actually connects
The modern way to connect is Embedded Signup — an OAuth-style flow where the business owner logs into their own Meta Business account and explicitly authorises a specific app (like Wovara) to create or link a WhatsApp Business Account for them. The business keeps ownership of the WhatsApp Business Account throughout; the connecting tool never receives the owner's Meta password, only a scoped authorisation. Embedded Signup also supports a coexistence path for businesses that already run a number inside the free WhatsApp Business app — that number keeps working there while the Cloud API connection runs alongside it, confirmed with a QR code scan from inside the app.
Templates, categories and the 24-hour window
Two rules define most of what's different about messaging through the Platform versus the consumer app. First, any message sent to someone who hasn't messaged you in the last 24 hours has to be a pre-approved message template — Meta reviews template content and assigns it a category (marketing, utility or authentication), each with its own pricing and policy treatment. Second, within that 24-hour window opened by the customer's own message, free-form replies are allowed without a template, which is what makes ordinary support conversations possible.
What this means for a business evaluating a WhatsApp CRM
Because the Platform itself is Meta's infrastructure, the core rules — templates need approval, the 24-hour window, conversation-based pricing — apply no matter which CRM or BSP a business connects through. What differs between tools is entirely the layer on top: how good the shared inbox is, how automation is built, and how clearly the tool represents what is and isn't included. It's worth being specific here: Wovara connects your number to the WhatsApp Business Platform and gives you the inbox, campaign and automation layer described throughout this site — that's a different thing from a general-purpose developer API for building your own custom integrations against Wovara itself, which is a separate, still-developing part of the product rather than something available today.
The takeaway
"WhatsApp Business API" describes Meta's messaging infrastructure, not any single company's product. Every legitimate WhatsApp CRM — Wovara included — is a layer built on top of that same underlying platform, connected the same official way, subject to the same messaging rules. The real differences between tools are in the software built around that connection, not in the connection itself.