What is a WABA?

WABA stands for WhatsApp Business Account. It is the container Meta uses to hold your WhatsApp Business API resources, and almost every question about getting started with the API is really a question about how that container is shaped.

What a WABA holds

A WABA is not itself a phone number, and it is not the WhatsApp Business app on someone’s phone. It is an account structure that owns two things you will interact with constantly:

• Phone numbers — the numbers messages are sent from. A number is registered to one WABA at a time.
• Message templates — the pre-approved formats Meta requires for business-initiated messaging, each carrying an approval status.

Because both live under the account, a WABA is the natural unit for organising WhatsApp infrastructure. It is also why platform pricing tends to be quoted per WABA rather than per number or per message.

WABA vs the WhatsApp Business app

The WhatsApp Business app is an app a person opens and types in. WhatsApp Business API has no interface at all — it is an interface for software. You do not "log in" to the API; your systems call it, and something has to render the results for humans.

That difference is the reason API setup feels heavier. The app needs a phone. The API needs a business, a verified account, a registered number, approved templates, and somewhere for events to land.

What you need before sending

• A Meta business that can be verified — Meta sets these requirements, and they change independently of any platform you use.
• A WhatsApp Business Account.
• A phone number registered to that account, which cannot already be active on the WhatsApp Business app.
• At least one approved template, if you are starting the conversation rather than replying.

How this maps to WA Console

WA Console connects an account you already own through Meta’s Embedded Signup, then syncs its phone numbers and templates so they are visible in one place. One organisation can hold several WABAs, and an API key is scoped to exactly one account — so a credential issued for one account cannot act on another.