Guides

The official WhatsApp API (Cloud API): what it is and how it works

What the WhatsApp Cloud API is, how it differs from the WhatsApp Business app, what a WABA is, how Meta bills messages, and when migrating is worth it.

Updated September 2, 2026

The Cloud API is the interface Meta hosts so businesses can send and receive WhatsApp messages from software, with no device kept online. It replaced the old On-Premises API and is now the standard — and the only officially supported — way to put a whole team, a system or an AI agent on one number.

How is it different from the WhatsApp Business app?

The app is built for one person on one phone. The API is built for a company: several people answering at once, one central history, integrations with CRM, ERP, website and agents.

WhatsApp Business app Official API (Cloud API)
Who answers 1 phone (+ up to 4 linked devices) the whole team, no device limit
Where it runs on the device on Meta servers
Integrations none any system, over HTTP
Messaging outside a chat manual approved template
Cost free per template message, billed by Meta
Ready-made interface yes comes from the platform you connect

The API has no screen of its own: it delivers messages. The inbox, the team roles and the reports come from the platform you put on top of it — for Nivox, through Meta's embedded signup.

What is a WABA?

WABA stands for WhatsApp Business Account: the container, inside Meta's Business Manager, that holds your numbers, your approved templates and your quality rating. It is created in your company's name. That matters for a practical reason: if you ever switch platforms, the WABA, the number and the approval history stay yours.

How does billing work?

Since 2025 Meta charges per message sent from a template, priced by category and destination country:

  • marketing — promotions, news, abandoned cart;
  • utility — confirmations, order updates, reminders for a service already bought;
  • authentication — verification codes.

Support messages — the ones you send inside the 24-hour window the customer opened — are not charged by Meta. The price list is published by Meta and applies to your account regardless of the platform. In practice, answering fast inside the window is cheap; depending on cold outreach is expensive.

What do you need to get started?

  1. A phone number that is not active on regular WhatsApp. If it lives in the WhatsApp Business app today, you can migrate it — or keep both through coexistence.
  2. A Meta Business Manager with your company registered. Business verification is required for higher volumes and some features.
  3. A platform connected to the Cloud API, which is what gives you the inbox, the roles and the integrations.

With Embedded Signup those three steps happen in one window, without leaving the site and without mailing tokens around.

When is migrating worth it?

When at least one of these describes your day:

  • more than one person needs to answer the same number, and the phone became the bottleneck;
  • support needs to know what is in your systems — order, stock, calendar;
  • you want confirmations and reminders to go out automatically, with nobody typing;
  • you want an AI agent answering the repetitive questions and handing the rest to a person.

If none of that applies yet, the app is enough. Past that point the official API is the way — and the official part matters: QR-code alternatives put the number at risk without offering anything the Cloud API cannot do.

Still have a question?

The FAQ covers pricing, Meta rules, team roles and agent access. The technical documentation is public and any AI agent can read it.