The requirements to connect your WhatsApp Business to the Official API

If you sell on WhatsApp and have already hit the ceiling of what the regular app can deliver, the answer is the Official API. But before you go looking for "how to set it up," it's worth understanding one thing: Meta doesn't grant access to just any number. There are specific criteria, and meeting all of them before you start keeps your process from stalling halfway through.

Here are the real requirements for connecting your business to the WhatsApp Official API in 2026.

1. A formalized business

The first filter is simple: Meta requires you to have a registered company, with a CNPJ or equivalent document. Personal profiles, informal businesses, or unregistered sole proprietors don't pass verification. If you're still operating informally, that's the first step before anything else.

A verified account on Meta Business Suite

All API access goes through Meta Business Suite (formerly Business Manager). That's where control over your WhatsApp Business Account (WABA), your permissions, and the rest of your assets on Meta are centralized.

Just having the account created isn't enough: it needs to go through Meta's business verification, which confirms you're a legitimate entity. At this stage, Meta may ask for documents proving your business's legal existence.

A dedicated phone number

The number you're going to connect to the API needs to:

• Be able to receive a code by SMS or voice call
• Not be linked to any other WhatsApp account (personal or Business) at the time of activation

If the number is already in use on the regular WhatsApp Business app, there's now an alternative that avoids losing everything: WhatsApp Coexistence, launched by Meta in 2026. With it, the same number operates simultaneously on the phone app and on the API, keeping the history and letting the manager keep replying from the phone while automation runs behind the scenes. Before this feature, migrating to the API meant uninstalling the app or using a new number, losing the conversation history.

A website with your own domain

It's not a formal, mandatory requirement, but it acts as a strong signal of legitimacy to Meta. Companies with their own website and a professional domain tend to get through approval faster. If you're still using just an Instagram bio as a "website," it's worth fixing that before starting verification.

Access via a BSP (Business Solution Provider)

You have two paths to access the API: create an application directly on Meta for Developers, or go through a BSP, an official partner certified by Meta.

In practice, going straight through Meta requires a dedicated technical team to handle webhooks, tokens and your own infrastructure. That's why most companies, especially those without an in-house development team, choose a BSP: the technology is still 100% Official API, just with an interface and support layer on top, which drastically cuts implementation time.

Claryflow operates as a certified Meta Tech Provider, meaning you connect your WhatsApp to the Official API without having to build your own infrastructure.

Approved message templates

To start conversations outside the support window (the well-known 24 hours after the customer's last message), every message needs to go through a template pre-approved by Meta. That applies both to confirmations and notifications and to bulk sends. Submitting and waiting for template approval is part of the process, not an optional step.

What is NOT a requirement

It's worth clearing up a common myth: the paid Meta Verified badge (the blue checkmark) is not required to activate the API. It's a visual perk, not an approval criterion. What really matters for approval is whether the business is formally established and verified in Business Manager.

Checklist recap

Before starting the process, confirm that you have:

• A company with an active CNPJ
• A Meta Business Suite account created and ready for verification
• A dedicated number, able to receive SMS/calls, not linked to another account (or ready to use Coexistence)
• A website with your own domain
• A decision on the access path: Meta for Developers directly, or through a BSP

You don't have to figure this out alone

Gathering documentation, setting up Business Manager, choosing the right templates, and still understanding all of Meta's usage policy takes time most businesses don't have to spare. That's exactly why BSPs exist: someone who's already been through this process hundreds of times handles the technical side while you focus on selling.

At Claryflow, this whole process happens inside the platform itself, with no need to open separate tabs or deal with technical setup elsewhere. In practice, it works like this:

• Click "Add connection" and select the "WhatsApp Official (Meta)" option
• Give the connection a name and click "Connect with WhatsApp Business"
• Log in with your Facebook account and follow Meta's own embedded signup: choose to connect an existing WhatsApp Business app and select the business account
• Add (or confirm) the number that will run on the API
• Accept the requested permissions
• Scan the QR code to validate the number
• Add the payment method required by Meta
• Complete the signup

Done: your number is now running on the Official API, straight through Claryflow.

FAQ

Do I need a CNPJ to use the WhatsApp Official API?

Yes. Meta requires the business to be formally registered, with a CNPJ or equivalent document. Personal profiles and informal businesses don't pass verification.

Can I use my personal number on the Official API?

You can, as long as it isn't linked to another WhatsApp account at the time of activation. If the number is already in use on the regular app, you don't have to abandon it: WhatsApp Coexistence lets you run the same number on the app and the API at the same time, without losing the history.

Will I lose my conversation history when migrating?

Only if you choose not to use Coexistence. Migrating with Coexistence active, the app's history stays on the device normally while the API starts operating in parallel.

Do I need the Meta Verified badge to activate the API?

No. Meta Verified is a paid visual perk, not a requirement. What Meta evaluates is whether the business is formally established and verified in Business Manager.

Can I set up the API myself, without a BSP?

You can, but it requires a technical team to handle webhooks, tokens and your own infrastructure directly on Meta for Developers. That's why most companies prefer a BSP: the same Official API, with an interface and support layer that cuts implementation time from weeks to minutes.

Does the Official API eliminate the risk of being banned for good?

There's no such thing as zero risk, but it drops drastically. The Official API is infrastructure authorized by Meta itself, unlike unofficial tools that operate outside the platform's rules.