WhatsApp Cloud API: The Complete Guide to Meta's Official API for UK Businesses

What is the WhatsApp Cloud API, how does it work, what does it really cost, and when is it worth it? We demystify Meta's official API without the jargon.

by Cleverson Gouvêa

WhatsApp Cloud API: The Complete Guide to Meta's Official API for UK Businesses

The WhatsApp Cloud API is Meta's official, free-to-host solution for businesses to communicate with customers at scale within WhatsApp. If you've ever got lost among acronyms like BSP, template, 24-hour window, and per-message pricing, this guide clears it all up: what it is, how it works, what it really costs, and when it makes sense for your business.

TL;DR

  • The WhatsApp Cloud API is hosted by Meta itself, with no server costs — you only pay for the messages you send.
  • From 1 July 2025, billing is per delivered message, not per conversation.
  • Customer-initiated conversations (service) are free and unlimited within the 24-hour window.
  • Sending limits start low (250 messages/day without verification) and increase with verification, quality, and volume.
  • The API is just the plumbing: you still need a customer service platform on top of it.

What the WhatsApp Cloud API Is (and What It Isn't)

The WhatsApp Cloud API is one of three ways a business can connect to WhatsApp as part of the WhatsApp Business Platform — Meta's suite of enterprise products. In practice, it's an application programming interface (API) that your business, or the software you use, employs to send and receive messages automatically, without anyone typing on a phone.

The key word is Cloud: unlike the older On-Premises version, Meta itself hosts all the infrastructure on its servers, free of charge. You don't maintain a server, update versions, or worry about uptime of the plumbing. This dramatically lowers the technical barrier to entry.

Now, what it isn't: the Cloud API is not an application. It has no screen, no inbox, no send button. It's an engine. For a human to respond, or for an AI agent to reply, you need a software layer on top — whether a ready-made platform or a custom system. Confusing the API with the complete solution is the number one mistake beginners make.

Cloud API, On-Premises, and Business App: The Three Entry Points

There are three official ways to use WhatsApp professionally, and choosing the wrong one costs time and money. The table below summarises the differences.

Feature WhatsApp Business App Cloud API On-Premises API
Who hosts Your phone Meta (cloud) Your server
Infrastructure cost Free Free Server + maintenance
Simultaneous agents Up to 5 devices Unlimited Unlimited
Real automation Limited Full Full
Status in 2026 Active Recommended Discontinued

The Business App is the free app from the store, ideal for micro-businesses with low volume — but it hits a wall when you need multiple agents and serious automation. The On-Premises API was the older version that ran on your server; Meta discontinued it and ended support in October 2025, migrating everyone to the cloud. So today, the WhatsApp Cloud API is the default choice for any operation that takes customer service seriously. If you're still unsure between app and API, check out our detailed comparison at WhatsApp Business App vs Official API.

How the WhatsApp Cloud API Works Under the Hood

Understanding three concepts resolves 90% of the confusion about the official API: templates, the 24-hour window, and webhooks.

Message Templates

You can't just send any text to someone who hasn't contacted you first. To start a conversation, the business must use a template (message model) pre-approved by Meta. Each template has a category — marketing, utility, or authentication — and that category determines what you pay. Templates are precisely what protect users from spam and maintain the quality of the ecosystem.

The 24-Hour Service Window

When a customer sends you a message, a 24-hour service window opens. Within that window, you can reply freely with any content, no template required, and — since November 2024 — at no cost. If 24 hours pass without the customer replying, you need a paid template to reopen the conversation. This mechanism is the heart of the cost model.

Webhooks

The Cloud API talks to your system via webhooks: every time a message arrives, Meta sends a notification to a URL you configure. That's how your platform knows the customer has replied and can trigger a human or AI agent in real time.

What It Costs: The Per-Message Pricing Model

This is where most myths live. Until mid-2025, Meta charged per conversation (24-hour blocks). From 1 July 2025, the model changed to per-message pricing: you pay for each template message that reaches the recipient, and the amount depends on the category and the country of the receiving number.

Category When Used Charge
Service (customer service) Reply within 24-hour window Free
Utility Confirmations, receipts, order updates Paid (free within window)
Authentication Verification codes (OTP) Paid, per message
Marketing Promotions and campaigns Paid, usually the most expensive

Two points that almost no one explains properly: first, service messages are free and unlimited — if your business is mostly reactive (customer calls, you reply), your messaging cost could be near zero. Second, Meta now offers volume-based discounts for utility and authentication templates. Rates vary significantly by country, so always check the official table for the category you use most.

To make this concrete, consider a shop that sends an order confirmation (utility) and the customer replies with a question. The confirmation within the open window may be free, and all subsequent service exchange is also free. A promotional campaign sent to a thousand contacts who haven't interacted recently falls under marketing — the most expensive category — and each delivered message is charged. The practical lesson is straightforward: the more your flow is service and utility, the lower the cost; the more it's cold marketing, the higher. Designing your flows with this in mind is what separates a lean operation from an expensive one.

Watch out for a hidden cost: the intermediary. Many platforms add a markup on top of Meta's price per message. At volume, this becomes significant. We detail this trap in Markup on WhatsApp Messages.

Sending Limits and Throughput: How to Scale Without Being Blocked

The WhatsApp Cloud API doesn't grant unlimited sending on day one — and that's intentional, to curb spam. Every new account starts at a low messaging tier and rises on merit.

  • Without business verification: 250 messages initiated per business in 24 hours.
  • Verified and with good quality: limits increase in steps — 1,000, 10,000, 100,000, and in some cases, unlimited.
  • Tier advancement: since October 2025, the limit is counted per Business Portfolio (not per number), and Meta reassesses upgrades every few hours.

There's also throughput, the sending speed. By default, the Cloud API processes about 80 messages per second, and high-tier accounts can reach 1,000 per second. For most SMEs, this ceiling is never an issue.

What gets accounts banned isn't volume per se, it's quality. If many people block or report your messages, your quality rating drops, the tier stops rising, and the number may be restricted. Since the official API reduces — but doesn't eliminate — this risk, it's worth understanding best practices in How to Avoid WhatsApp Business Number Blocking.

How to Get Started with the WhatsApp Cloud API: Step by Step

Technically, you can set up a test number in minutes. For production, the path is as follows:

  1. Meta Business Manager account — the central dashboard where everything is managed.
  2. Business Verification — submit company documents; this unlocks higher limits.
  3. WhatsApp Business Account (WABA) — created within Business Manager.
  4. Number registration — a phone number that is not linked to a regular WhatsApp or Business App. This trips many people up.
  5. Template approval — submit and wait for Meta's review.
  6. Webhook configuration — to receive replies in your system.

When NOT to do this yourself: if you don't have a development team, integrating the raw API is a lot of work and ongoing maintenance. In such cases, hiring a platform that already delivers everything on top of the Cloud API is often cheaper than maintaining a custom system.

Common Mistakes That Get Accounts Banned on the Cloud API

After deploying the WhatsApp Cloud API in dozens of operations, the same pitfalls keep recurring:

  • Using a personal number already active on regular WhatsApp. A number registered on the API cannot exist simultaneously on the normal app. Migrating requires deleting the old account for that number.
  • Treating marketing templates as service. Sending promotions to people who didn't ask for them destroys your quality rating and increases cost.
  • Ignoring the 24-hour window. Trying to reply outside it without a template simply won't deliver.
  • Buying the API thinking it's the final solution. Without a customer service layer on top, you have an engine without a car.
  • Neglecting the template category. Registering something as utility that is clearly marketing leads to rejection or reclassification by Meta, and can make what seemed cheap expensive.

The good news is that all these mistakes are avoidable with planning. Most of them, in fact, disappear when you use a platform that abstracts registration, categorisation, and respect for the 24-hour window. If your number has ever been restricted, migrating to the official API is usually the safest way out — a topic we explore further in WhatsApp Blocked: The Official API Is the Way Out.

The Cloud API Is the Engine, Not the Car

It's worth repeating, because it's the most expensive misunderstanding: the WhatsApp Cloud API alone doesn't serve anyone. It transports messages. The platform that organises queues, distributes conversations among agents, keeps history, triggers automations, and puts an AI agent to work 24/7 is what runs on top of the API.

That's precisely the role of solutions like Voyia, which use the official API underneath and deliver the complete customer service experience — without you having to handle webhooks, templates, and Business Manager manually. If your team is currently paying per agent, it's worth seeing why that model no longer adds up in Unlimited Agents on WhatsApp.

Conclusion: When the WhatsApp Cloud API Makes Sense

If your business needs multiple agents, real automation, and wants to stay on the right side of Meta's rules, the WhatsApp Cloud API is the way to go — free to host, pay only per message, and increasingly with free service conversations. The secret is to stop seeing it as a final product and treat it as the foundation on which you (or a partner) build your customer service.

The next step is simple: list today how many agents and what message volume you actually have. With those two numbers in hand, it's easy to decide between the Business App, the raw API, or a ready-made platform — and stop paying for what you don't use.