The official WhatsApp Business API: what it is, how to get it and what it costs in 2026

What the official WhatsApp API is

Its official name is WhatsApp Business Platform. It's Meta's set of APIs for businesses that talk to customers at scale: send and receive messages, manage templates, numbers and profile, and get a webhook for everything that happens to each message. When people say “WhatsApp API”, “WhatsApp Business API” or “official WhatsApp API”, this is what they mean.

In 2026, that platform is the Cloud API, hosted by Meta itself. There used to be a version businesses installed on their own servers, the On-Premises API. It stopped accepting new sign-ups in July 2024 and shut down for good on October 23, 2025, when the last version expired and the numbers still on it stopped sending and receiving messages. Today, the official WhatsApp API and the Cloud API are the same thing.

The API carries messages between WhatsApp and a system. Meta offers a dashboard to manage accounts, numbers and templates, WhatsApp Manager, but the conversation with the customer happens in the software connected to the API: yours, if you have the engineering team to build it, or a provider's, which delivers the team inbox, automations and reports on top of it.

The platform page describes exactly these two paths: connect directly, if you have developers, or sign up through a Meta partner. Either way, access to the Cloud API is free. What you pay for is messages, and, when there's a provider, what it charges for what it builds around them.

WhatsApp Business app or API: what changes

The WhatsApp Business app is free and was built for small businesses that serve customers from a phone. It has a business profile, catalog, labels, greeting message, away message and quick replies. The number lives on a primary phone, which can be linked to up to four devices, and the whole team answers from the same handful of screens.

The API replaces the phone with a system. There's no limit on how many people can answer on the same number, because they work in the software, not on a linked device. Conversations can be routed through queues, answered by automation or AI, and connected to the store, the ERP and the CRM. And the business can start the conversation with approved templates, such as an order update or a verification code.

The rule that surprises people coming from the app the most is the customer service window. When a customer writes in, a 24-hour window opens in which the business can reply with anything. Outside it, only Meta-approved templates go out. The app has no such rule; in the API, it decides what can be sent and what it costs.

And you don't have to pick one. Since 2025, coexistence lets you use the same number in the app and the API at the same time, with app version 2.24.17 or later and the connection made through a partner's sign-up flow. The owner stays on the phone, the team moves to the inbox, and the chat history comes along, once. We cover the details in our post on coexistence.

Official vs. unofficial: what the “unofficial API” is

“Unofficial WhatsApp API” is the sales name for software that automates regular WhatsApp or WhatsApp Web: you scan a QR code, and a server starts sending and receiving messages as if it were your phone. It's sold as cheaper, with no templates and no Meta charges. It isn't a WhatsApp API; it's the app being run by a bot.

WhatsApp's Terms of Service prohibit exactly this. In the section on harm to WhatsApp and its users, they bar accessing or using the service through automated means without authorization. In the acceptable use section, they bar bulk messaging, automated messages and non-personal use without authorization. And WhatsApp can suspend or disable the account at any time. In practice, the risk is a ban on the number your customers know.

There's also what app automation can't do. There are no templates, so there's no way to reach someone who hasn't written in the last few hours without looking like spam. There's no reliable delivery confirmation, the session drops when the phone disconnects, and your customers' conversations pass through a server with no commitment to any data protection law (GDPR in Europe, LGPD in Brazil). The low price comes from having none of the official platform's guarantees.

How to get access to the API, step by step

The first step is a business portfolio at Meta, formerly Business Manager. That's where the WhatsApp account, the numbers and the payment method live. If you're connecting directly, you also need a developer account and an app in Meta's developer dashboard; if you go through a partner, you do everything in its sign-up flow, Embedded Signup, in a few minutes and with your own Facebook login.

Business verification isn't required to start, but it's the first unlock that matters. With a verified portfolio, you can go from 2 to 20 numbers, raise the template cap per messaging account, apply for the Official Business Account badge and move past the initial limit of 250 people a day. Meta checks the business details, such as legal business name, address and website, against documents.

The number must be yours, with country and area code, and able to receive a code by SMS or voice call. Short codes don't work. If the number is already in use on WhatsApp, Meta asks you to delete that account first, unless the path you choose is coexistence. The display name, what the customer sees, is entered at sign-up and goes through automatic verification when the limit goes up and with every change.

With the number live, what's left is templates: the messages the business sends outside the customer service window. Each template is approved by Meta and classified in a category, marketing, utility or authentication, and the category sets the price. Finally, the blue Official Business Account badge is optional: it requires 30 days on the platform, a verified portfolio, two-step verification and an approved display name.

How much the official WhatsApp API costs

Using the API has no monthly fee from Meta. What Meta charges for is messages: since July 1, 2025, each delivered message has a price that depends on the category and the recipient's country. There are three template categories, marketing, utility and authentication, each with its own rate card. Utility and authentication get volume-tier discounts within the month; marketing doesn't.

Free-form replies, which Meta calls service messages, were free from November 2024 to September 2026. Since October 1, 2026 they're charged too, with an allowance of 1,000 free service messages per number per month, which doesn't roll over. On the same day, utility templates sent while the customer service window is open became billable again.

In Brazil, local-currency (BRL) billing is being phased in. It started on July 1, 2026 for businesses billed in Brazil, with the invoice issued by Facebook Brasil, and every account in the portfolio has to move over by June 30, 2027. From July 1, 2027, Meta stops delivering messages for accounts that are still on another currency.

On top of that comes the provider's pricing model, and that's where market prices diverge. Some charge a flat monthly fee, some charge per agent, some per active contact, some pass through Meta's rate card in dollars and some publish a per-message price in local currency. Comparing only the per-message rate hides most of the bill.

The fair comparison is the monthly bill: your volume by category, the number of people who will handle conversations, the currency the invoice comes in and what's charged separately, like inbox, automation and AI. A provider that charges little per message and a lot per agent can end up costing more for a large support team, and the opposite holds for a business that only sends notifications.

The limits: how many people and how fast

The limit you hear about most is the messaging limit, and it doesn't count messages: it counts people. It's the number of unique recipients you can reach outside the customer service window in a rolling 24-hour period. Replying to people who wrote to you uses none of it. And since October 2025, the limit belongs to the whole portfolio, shared across all its numbers.

A new portfolio starts at 250 people a day. The step up to 2,000 comes with business verification or with 2,000 high-quality messages delivered outside the window in 30 days. After that, the ladder is 10,000, 100,000 and unlimited, and it climbs on its own, within six hours, when message quality is high and the portfolio has used at least half its limit in the last seven days.

Throughput is the other ceiling. Each number sends up to 80 messages per second by default and can scale on its own to 1,000, as long as the portfolio is at the unlimited tier, the number has messaged 100,000 people in 24 hours and the quality rating is yellow or better. A coexistence number, used in the app and the API at the same time, is fixed at 20 per second.

Quality ties the two ceilings together. Meta measures how customers react to your messages, with blocks and reports counting against you, and uses that to release or hold the limit ladder. Templates that annoy people drag quality down, and low quality stalls growth for the whole portfolio, not just the number that sent them.

What changed in 2026 and what changes in 2027

On September 23, 2026, the new account model took effect. The WhatsApp Business account splits in two: a WhatsApp account, which holds the number, and a messaging account, with the templates, billing and webhooks. As a result, the same number can be shared with more than one provider, and switching providers is no longer a number migration.

On January 15, 2026, Meta's rule for AI providers took effect. General-purpose assistants, such as chatbots built on large language models, can't use the platform when AI is the main functionality. In Brazil, general-purpose assistants have been accepted since March 11, 2026, paying per service message. A business's own customer service AI, which answers questions about its products and orders, is still allowed, according to Meta, and the messaging policy calls for a path to a human agent.

On October 13, 2026, Meta announced the end of marketing on the Cloud API. Messaging accounts created on or after April 13, 2027 can no longer send marketing through it, and on October 13, 2027 the Cloud API stops accepting marketing altogether. Marketing moves to the Marketing Messages API, and that applies to every provider.

Finally, usernames. In 2026 Meta started rolling out usernames on WhatsApp, which let a person talk to a business without showing their phone number. Webhooks now carry a per-portfolio identifier, the BSUID, which has worked for sending messages since July 2026. For anyone who identifies customers by phone number, as most CRMs do, it's a data-model change worth preparing for ahead of time.

How to choose a provider

The API is the same at every provider: the same limits, the same categories and the same window rules. What changes is what each one builds on top and how it charges. That's why the questions worth asking are about your operation, not about the API.

Ask what currency the invoice comes in and who issues it. Ask whether there are charges per agent, per contact or per number, and whether the per-message price is published or only shows up in a proposal. Ask whether the provider supports coexistence, so you don't lose the app, and what happens to the number and the history if you ever want to leave.

Also ask where the conversations are stored, because they're your customers' personal data and data protection law (GDPR in Europe, LGPD in Brazil) applies to them. And if AI is in the plan, ask how it hands the conversation to a person, what it can do on its own and what needs approval. A provider that answers these questions in writing before the sale usually answers the same way after it.