Meta verification and WhatsApp API approval

Who actually needs the WhatsApp Business API?

The WhatsApp Business app on a phone is enough for a small business: one number, one device, messages typed by hand. The API answers a different need — messages sent by a system. Order status notifications, appointment reminders, support requests logged into a ticket, or an AI agent taking over the conversation are only possible with the API.

The distinction becomes clear here: is a human writing the message, or is a system triggering it? In the second case you need the API, and the API does not open without a verified business account. So there is a paperwork process before any technical integration.

What does Meta business verification ask for?

In one sentence: proof that you are attached to a legal entity. Meta compares the legal name, address and phone number on the business account against the official document you upload, and may also require domain verification. The process typically takes a few business days.

In most rejected applications the problem is not the document but the spelling. The name in the Meta account must match the trade registry exactly; abbreviations, a missing legal form suffix, an outdated address and documents evidencing an individual are the most common causes. Before applying, open your registry record and copy the fields letter by letter — that alone removes a multi-day delay.

What are the steps after verification?

This order cannot be skipped. Templates cannot be submitted before the number is registered, and the display name does not go to review before verification completes. When planning, treat this chain rather than the technical integration as the critical path; the code takes a day, the chain can take a week.

How does pricing work?

Cost depends on the template category of the message you send. Marketing, service and authentication categories are priced differently, and prices also vary by country. That takes budgeting out of a simple “x per message” formula: two products with the same volume can produce very different bills purely from category mix.

The practical consequence is that message design is a cost decision. If a notification flow can be built in the service category rather than marketing, it is both cheaper and easier to get through template review. Do not choose the category arbitrarily — the content of the message determines the category, not you.

Three habits that protect the account

First, consent: capture permission explicitly inside the product for every number you will message, and keep that record. Second, exit: leave a way for the user to stop the conversation in every message. Third, pace: do not send high volume from a newly registered number on day one.

These are not merely polite; they are what keeps the account alive. User complaints lower the account's quality rating and messaging limit, and once the limit drops, the functional notifications you actually care about stop going out too. A badly constructed campaign therefore cripples your order-notification flow as well.