What Is the WhatsApp Cloud API?

Until recently the WhatsApp Business Platform came in two shapes. The On-Premise API shipped as software you hosted yourself — your servers, your uptime, your upgrade cycle — which suited enterprises with strict data-residency requirements and nobody else. The Cloud API moved all of that onto Meta's infrastructure. You call an endpoint, Meta handles scaling and version upgrades, and new platform features are available without a migration project. Meta has been retiring the On-Premise option, so for practically every business starting today, "the WhatsApp Business API" and "the Cloud API" mean the same thing.

These are not alternatives in the way people often assume — a Business Solution Provider sits on top of the Cloud API rather than replacing it. Going direct gives you raw API access and nothing else: no shared inbox, no campaign builder, no template manager, no contact database, no reporting. Everything a team actually operates day to day is yours to build. A provider gives you those as an application, along with help through Meta Business verification and template approval. The right choice is mostly about whether you have engineering time to spend: a developer-heavy team that wants full control goes direct; a business that wants to send campaigns next week does not.

Access to the Cloud API itself is free — there is no licence fee for the endpoint. What you pay for is conversations. Meta bills per 24-hour conversation window rather than per message, at a rate that depends on the conversation category (marketing, utility, authentication or service) and the country the recipient is in. That distinction catches most first budgets: five messages to one customer inside a day is one billable conversation, and the same campaign costs materially different amounts in different markets. Conversations a customer starts are treated differently from ones your business starts, which is why answering people is cheap and reaching out is not.

Cloud API removes the hosting problem, not the compliance one. You still need a verified Meta Business account, a display name that survives review, a phone number that is not registered anywhere else, message templates approved before you can start conversations, and recorded opt-in for everyone you message. Your quality rating still governs how many customers you may message per day and still falls when people block or report you. Hosted infrastructure changes none of that.

If you signed up with a platform, scanned nothing, and were guided through Meta Business verification, you are on the Cloud API through a provider. If your engineering team runs a container and manages webhook endpoints directly, that is either direct Cloud API access or a legacy On-Premise deployment worth checking on. If you scanned a QR code to link an existing WhatsApp account to a desktop tool, you are on neither — that is unofficial automation of the consumer app, and it is what gets numbers banned.

• Reputoo sends on the official WhatsApp Business Platform, so template rules, opt-in and quality rating behave exactly as Meta documents them
• Meta Business verification, display-name review and template submission are handled as part of onboarding rather than left to you
• The inbox, campaigns, automations and reporting that direct Cloud API access does not include come with the platform
• One AI agent answers on WhatsApp and on phone calls, reading your own services, prices and availability