What is the WhatsApp Business API? A plain-English explainer

Updated 2026-09-19 · 5 min read · By the Convo360 team

The core definition

The WhatsApp Business API is Meta's infrastructure that lets a business's software send and receive WhatsApp messages programmatically, a chatbot replying automatically, a notification firing when an order ships, an agent viewing conversations in a shared team inbox. It is not something you download and open; it's a set of capabilities a platform builds on top of.

This is the key difference from the regular WhatsApp Business app, which is a free download with its own chat screen for one phone, used by small shopkeepers and solo service providers.

How it actually works, mechanically

Underneath, the API works through webhooks in both directions: when a customer messages your number, Meta sends that message to your connected platform as a webhook event; when you want to reply or send a template, your platform calls Meta's API with the message content. There's no phone app polling a screen. Every message is an API call, which is exactly what makes automation, a shared team inbox and integrations with a CRM or order system possible in the first place.

Two rules shape day-to-day use: outside a customer's last message you can only send pre-approved templates, not free text, and within the 24-hour customer service window after a customer writes to you, you can reply with anything. This single mechanic is why chatbot platforms are built around templates and flows rather than plain messaging.

Who actually needs it, especially in India

A solo tailor or a neighbourhood kirana store replying to a handful of customers a day is well served by the free app. For a growing Indian SME, the API becomes necessary once any of the following applies:

• Automated replies or a chatbot handling common questions after hours
• Sending notification templates (order updates, appointment reminders, payment links) outside an active chat
• Multiple team members working from one shared number with a proper inbox, instead of passing round one phone
• Integration with a CRM, order system or booking calendar

If any of these apply, the app alone won't scale: a single phone number can only be logged in on one device at a time, and there's no way to route conversations to different staff or trigger a message automatically from another system. The API is what makes automation possible.

This shows up concretely for an Indian business the moment order volume crosses a few dozen a day: a shop owner manually typing 'your order has shipped' to each customer from the app quickly becomes the bottleneck, while the same update sent automatically the moment a courier status changes needs no manual typing at all.

The app, the API and a BSP-connected platform compared

How access actually works

Getting access used to require going through a Business Solution Provider with a lengthy approval process. Today, embedded signup lets a business connect its own WhatsApp number to a platform like Convo360 directly from within the platform, verifying the business and linking the number in one guided flow, without a separate approval wait. See what a BSP does if you want the fuller picture of that older model.

The business keeps ownership of its own WABA (WhatsApp Business Account) throughout. The platform doesn't own the number or the account, it just provides the tools to use it. This matters more than most businesses realise at signup time, since it determines whether you can move to a different platform later without losing your template history and quality rating.

Common misunderstandings

The most common mistake is assuming the API is a separate, more expensive WhatsApp product with its own subscription to Meta. In reality, Meta bills per delivered message, by template category (Marketing, Utility or Authentication), at rates set per country. There is no separate 'API licence fee' from Meta itself, though platforms built on top typically charge their own subscription for the tools. See our WhatsApp Business API pricing in India guide for the current rates.

A second common mix-up is thinking a number can run on both the app and the API simultaneously. It can't, moving a number to the API means it comes off the regular app. A third is assuming that connecting through any platform automatically means losing control of the WhatsApp number; this depends entirely on whether the WABA is created under your own Meta Business Manager, which embedded signup does correctly.

A fourth, subtler misunderstanding is expecting the API to allow open-ended marketing messages the way a personal WhatsApp chat does. Every template still needs Meta's approval, and outside the 24-hour service window a business genuinely cannot send free-form text, planning your flows and templates around this constraint from day one avoids a lot of rework later.

How this looks on Convo360

Convo360 connects to the WhatsApp Business API through embedded signup, then gives you the Flow Builder, WhatsApp Studio for templates, and a team inbox on top of it, all under BYOK, meaning the WhatsApp number and Meta billing stay under your own business account with no per-message markup added. See /docs/whatsapp/ for the full connection walkthrough, and Meta's own reference at developers.facebook.com for the technical detail behind it.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.