WhatsApp Business API Explained (Cloud API, On-Premise, and BSPs)

The WhatsApp Business API isn't one product, it's three different ways of connecting a business to WhatsApp, and most confusion online comes from writers mixing all three together as if they're interchangeable. Here's the plain-English map: Cloud API (run by Meta directly), on-premise (self-hosted, mostly legacy at this point), and Business Solution Providers, or BSPs (companies that sit between you and Meta and add their own tools on top).

The Three Flavours of the WhatsApp Business API

Think of it like renting an apartment versus owning a building versus using a property management company. Cloud API is Meta hosting the connection for you directly, free at the infrastructure level. On-premise means you run WhatsApp's server software yourself, which almost nobody chooses anymore given how much simpler Cloud API is. A BSP is a company that has already built the Cloud API connection and rents you access to it, usually bundled with a dashboard, chatbot builder, or CRM features.

Knowing which of the three you're actually being sold matters, because a sales page that just says "WhatsApp API access" could mean any of them, and the pricing model attached to each is completely different.


Cloud API in One Paragraph

Cloud API is Meta's own hosted version of the Business API. You apply through Meta, verify your business, and once approved you get direct API access with no BSP in the middle. There's no software to install and no server to maintain; you just send HTTP requests to Meta's endpoint. This is the version most modern platforms, including WaSMS, connect through, since it's faster to set up and doesn't add a middleman's markup.

curl -X POST "https://graph.facebook.com/v19.0/PHONE_ID/messages" \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"messaging_product":"whatsapp","to":"1555...", "type":"text","text":{"body":"Hi there"}}'

Approval through Cloud API typically takes anywhere from a day to a couple of weeks depending on how quickly Meta reviews your business details, and once approved, the connection itself is instant and stable.

On-Premise: Who Still Uses It

The on-premise API required running WhatsApp's own server software on your own infrastructure. Meta has been pushing everyone toward Cloud API for years, and on-premise is effectively legacy at this point, kept alive mostly by large enterprises with existing infrastructure investments they haven't migrated yet. For a new setup in 2026, there's essentially no reason to choose it over Cloud API: it requires more maintenance, more security responsibility, and Meta itself has stopped actively developing new features for it.

BSPs: The Middlemen

A BSP (Business Solution Provider) is a company Meta has approved to resell and build on top of the Cloud API. They handle the technical connection and usually add a dashboard, chatbot tools, or a CRM layer, then charge a monthly fee or per-message markup on top of what Meta itself charges. This isn't a bad model, it's genuinely useful for teams who don't want to touch an API directly, but it does mean paying two layers of cost: the BSP's fee plus Meta's own conversation pricing.

See platform comparison for how specific BSPs price out against a direct Cloud API connection through a platform like WaSMS. In practice, the BSP markup ranges from a flat monthly subscription to a per-conversation fee stacked on top of Meta's own rate, so it's worth comparing the total cost, not just the sticker price of the platform's cheapest plan.

Which WhatsApp Business API Fits Your Business

If you have any technical capacity at all, connecting directly to Cloud API through a platform that doesn't add a BSP markup, like WaSMS's Cloud API connection, gives you the same functionality most BSPs sell without the extra layer of cost. If you have zero technical resources and want someone else to fully manage everything for you, a BSP with a polished dashboard might be worth the premium. On-premise almost never makes sense for a new setup today.

For teams that don't want to go through Meta's business verification at all yet, a local gateway connection using a phone-based bridge is a middle ground worth knowing about, though it has different rate limits than the official API and suits lower-volume use cases better than high-volume marketing.

Pricing Basics

Meta charges per conversation category (marketing, utility, authentication, service), not per message within an open conversation window. That means a customer can send you ten messages inside one open conversation and it's still billed as a single conversation, not ten separate charges. A BSP adds its own subscription or markup on top of that base rate. Running Cloud API directly, without a BSP fee layered in, means you only pay Meta's base conversation rate, which is the model WaSMS uses to keep the WhatsApp connection free for the business owner beyond what Meta itself bills.

The Verification Process, Step by Step

Getting approved for Cloud API involves a handful of steps that trip people up mostly because nobody explains them plainly beforehand: creating a Meta Business Manager account if you don't already have one, verifying your business details (legal name, address, and a document proving the business exists), adding and confirming a phone number that hasn't been used on personal WhatsApp before, and submitting a display name for review. Most of the wait time is Meta reviewing the business verification step, not the technical connection itself, which is usually instant once approval comes through.

Common Confusions Worth Clearing Up

People often assume the WhatsApp Business API is a different app they need to install, when really it's just a way of connecting software to WhatsApp's servers with no consumer-facing app at all; all the interface work happens in whatever platform, like WaSMS, sits on top of the connection. Another common mix-up is assuming a phone number can run the personal app and the Business API simultaneously; once a number is migrated to the API, it can no longer send or receive through the regular consumer app on a phone.

A third confusion worth clearing up: people sometimes assume "Cloud API" and "WhatsApp Business Platform" are two different things, when Meta has used both names for essentially the same underlying product at different points, which is part of why so much of the terminology online feels inconsistent from one source to the next.

Choosing a Platform on Top of Cloud API

Once you've decided Cloud API is the right layer, the remaining decision is which platform you connect through, since Meta itself doesn't provide a dashboard, team inbox, or automation builder out of the box. This is exactly the decision covered in WhatsApp business platform comparison, and it's worth reading before signing up anywhere, since the platform layer is where most of the ongoing cost differences between providers actually live, not in Meta's own conversation pricing.

Skipping this step and picking the first platform that appears in a search result is how many businesses end up locked into a per-agent contract they didn't need to sign, simply because nobody explained that Cloud API access itself was available without that markup in the first place.

What to Read Next

If you're ready to connect, the practical steps are in how to connect WhatsApp Cloud API. If you want to compare specific BSP platforms side by side, see WhatsApp business platform comparison. And for the bigger picture of what a business actually needs on WhatsApp beyond just the API connection, read WhatsApp for business: the complete guide.