WhatsApp Cloud API: what it is and how to use it in a business

The WhatsApp Cloud API is Meta's official interface for a business to connect its WhatsApp to management software. Instead of replying from a single phone, messages go into a system where the whole team can work. Meta hosts it in its cloud: you don't maintain servers or install anything, and you're still using the official channel, with Meta's rules.

The most common confusion is believing that the API is a product you use on its own. It isn't. The API is a channel: it transports messages. What replies, organizes and learns is the software connected on the other side. That distinction explains almost every question that comes up afterward: why it doesn't answer on its own, why you have to pay per conversation, and why the provider you choose changes the experience so much.

What a BSP is and why it comes up in every conversation

BSP stands for Business Solution Provider: a provider authorized by Meta to give access to the API and support the integration. For years they were the only way to connect a number to WhatsApp Business. Today Meta also allows connecting directly to the Cloud API, but the BSP figure is still alive because most businesses don't want to deal with the technical part.

In practice, a BSP takes care of business verification, number connection, template management and support when something breaks. The trade-off is that it often adds a layer of cost or dependency. That's why it's always worth asking what the service includes and what happens if you want to migrate the number to another provider later on. That question, asked before signing, saves headaches afterward.

Cloud API, On-Premises and unofficial API: how they differ

Meta offers two official versions. The Cloud API is hosted in its cloud: you activate it, connect the number and that's it. The On-Premises version (now being retired) required the business to set up and maintain its own infrastructure, something that only made sense for large companies with their own technical team. For an SMB, the Cloud API is the reasonable option.

Then there's the unofficial route: libraries and services that connect to WhatsApp without going through Meta. They tend to be cheaper and faster to set up, and that's why they're tempting. The problem is that they violate WhatsApp's terms of use and put the number at risk: you can lose access to your contacts overnight, without notice and without recourse. The Cloud API is the only official and stable route.

• Cloud API: hosted by Meta, no own servers, it is the official recommended path for SMBs.
• On-Premises: own infrastructure, intended for large companies with a technical team. Being phased out.
• Unofficial API: not authorized by Meta, puts the number and contacts at risk.
• WhatsApp Business App: free, for a single device, without integrations or API.

How a business connects, step by step

The path has more steps than it seems, and almost all of them are about verification, not programming. If you go with a platform that is already connected to the API, it handles most of them for you. If you go on your own, you handle them yourself. The typical order is this:

1. 1Have a phone number that is not in use on the WhatsApp app or on WhatsApp Business. If it is active on the app, it must first be deactivated there.
2. 2Create or verify the business in Meta Business Manager. Meta asks for tax and company details; review times vary depending on the case.
3. 3Register the app in Meta for Developers and obtain the access credentials (the app identifier and the keys).
4. 4Connect the number to the Cloud API and verify ownership by code.
5. 5Set up the webhook: the address to which Meta sends incoming messages. Without this, messages arrive but nobody sees them.
6. 6Create and send the templates you will use to contact customers outside the 24-hour window.
7. 7Test the full circuit: incoming message, reply, template and log in the dashboard.

How much it costs to use the WhatsApp Cloud API

Here it is worth separating two things that are constantly mixed up: what Meta charges and what the platform you use to manage messages charges. They are two different bills.

Meta charges per conversation, not per message or per subscription. The price depends on the recipient's country and on whether the conversation was started by the customer or the business. Values change over time and vary by market, so the only valid reference is Meta's official documentation. There is no fixed monthly Meta fee for using the API.

A platform, on the other hand, usually charges a subscription. Wando, for example, has a 14-day free trial with no card required, and plans from US$12.99 per month, with a 25% discount on the first month. The updated details are at wando.online/pricing. The advantage of a platform is that it saves you development and maintenance; the disadvantage is that you add a fixed cost on top of Meta's.

• Meta: charges per conversation, depending on the country and who starts it. No fixed subscription.
• Management platform: charges a monthly subscription and provides the interface, the inbox and the features.
• In-house development: no subscription, but with the real cost of programming and ongoing maintenance.
• The total bill is the sum of the first two, not a single one.

What you can do once connected

With the API connected, the possibilities depend on the software you choose. In the case of Wando, which uses Meta's official API, the features are concrete: a message inbox where the AI suggests replies that the team approves with one click, HSM templates and campaigns, contacts with tags, message and campaign statistics, multi-agent, schedule-based auto-replies and audio transcription.

The differentiator is not the list of features, which is similar across tools, but how it learns. Wando's AI is trained on the real replies the business gives: if an agent corrects a suggestion before sending it, the system takes it into account for the next one. It is not a flow-based chatbot that you have to program branch by branch and maintain every time a price or a schedule changes. And by default it does not reply on its own: it suggests, and a person approves.

It also connects with other tools via webhooks to Make, Zapier, n8n and Slack, lets you export contacts to Google Sheets and take payments with Mercado Pago. In addition to WhatsApp, it adds Instagram and Messenger as channels. That expands your reach without forcing you to open a new inbox for each network.

A concrete example: a real estate agency that stops losing inquiries

A real estate agency in Córdoba receives WhatsApp inquiries about rental properties, especially outside office hours. Before, messages landed on one person's phone and Sunday's messages were answered on Monday. With the API connected to Wando, everything goes into a shared inbox.

When someone asks about an apartment, the AI suggests a reply with the property details. The agent reviews it, adjusts it if needed, and sends it. That correction is recorded and improves the following suggestions. Outside business hours, an auto-reply lets them know they will get an answer in the morning, and voice messages are transcribed so no one has to listen to them in full.

To notify about a scheduled visit, they use an approved template, because the business initiates the contact and that requires a template. The results show up in the message and campaign statistics. All of this without writing a single line of code and without the AI replying to anything without someone approving it.

The limits worth keeping in mind

The API has rules, and not all of them can be worked around. The most important one is the 24-hour window: when the customer writes, a period opens in which the business can reply freely. After that deadline, you can only reach out with a template approved by Meta. This is not a limitation of the software you use: it is how the channel works.

Template approval can take up to 48 hours. There is no way to speed it up or guarantee that a template will be approved: Meta reviews the content and can reject it. So if you have a campaign with a fixed date, it is best to prepare the templates with time to spare and not on the same day.

The other limit is usage. The API is not for sending bulk messages without consent. Meta monitors the behavior of numbers and can restrict or revoke access if it detects abusive practices. A business that grows with clear rules has no problem; one that buys contact lists does.

When NOT to switch to the API

If you handle fewer than ten messages per day and you do it alone, the free WhatsApp Business app is enough. The API adds a subscription and some initial complexity that are not justified with that volume. The same applies if you do not want to pay for a platform and also do not have a technical team: the raw API requires programming and maintenance, and that costs time or money.

It is also not a good fit if your strategy relies on contacting people who did not message you, without templates or consent. There the problem is not technical: it is that the channel was not designed for that, and Meta controls it.

On the other hand, if you already have more than one person replying, if messages get lost on weekends, or if you need to measure how long it takes you to respond, the API stops being a luxury and becomes infrastructure.

How to choose who to connect with

The API is the same for everyone; what changes is who provides it to you. Before deciding, it is worth looking at five specific things and asking for answers in writing.

• That it uses Meta's official API. If the provider does not say so explicitly, ask: unofficial services put your number at risk.
• What happens to your number if you want to leave. The number and the contacts are yours, not the provider's.
• What support includes and in what language and hours. For a small business in LatAm, local support changes the experience.
• Whether the AI suggests or replies on its own. For most businesses, human oversight by default is an advantage, not a limitation.
• Whether you can try before paying. Wando, for example, offers 14 days of trial without a card.

The underlying question is not which API to use, because there is only one. It is what software you put on top of it and whether that software learns from your business or forces you to program everything again every time something changes.

Common mistakes when understanding the Cloud API

One: believing that the API is free. Meta charges per conversation and prices vary by country; there is no fixed Meta subscription, but there is a variable cost that must be budgeted according to volume.

Two: thinking that the API responds on its own. It is a channel, not a bot. You need software that manages conversations and, if you want to automate, a system that suggests replies with human supervision.

Three: expecting template approval to be instant. It can take up to 48 hours, and planning campaigns without that margin is the most common way to get frustrated with the API.

Four: forgetting that Meta's prices change. Any number you read on a blog may be outdated; the valid reference is always the official documentation. And five: choosing a provider based on price and later discovering that the number cannot be migrated. That conversation is better had beforehand.