To activate the WhatsApp Business API you need a Meta business portfolio, a WhatsApp Business account, a phone number you own that can receive a call or SMS, a display name and a payment method. Business verification is not the first gate, but it is what lifts you from 250 to 2,000 recipients a day, so treat it as part of the job rather than an optional extra.
This guide covers the requirements in the order they actually bite, the decision about your existing number, what changes after verification, the checks to run before your first campaign, and when the API is the wrong step.
What you need before you start
A business portfolio. Everything hangs off a Meta business portfolio, the container formerly known as Business Manager. Use the one your company already has for ads if it exists. Creating a second portfolio to keep things tidy usually creates work later, because limits and verification are set at portfolio level.
A route onto Cloud API. Meta has retired the self-hosted On-Premises API, so a new activation runs on Cloud API, either directly through your own Meta app or through a Business Solution Provider that onboards you with Embedded Signup. The technical result is the same API. The difference is who builds and operates the layer on top, which is why choosing a BSP deserves its own decision.
A website that matches the company. Verification compares your portfolio details with what is publicly visible. A site on your own domain, showing the same legal name as your documents, removes the most avoidable source of delay.
A payment method. Meta bills per delivered message. Without a payment method on the account, Meta delivers Service messages only inside the monthly free tier and stops delivering them after it. The full breakdown is in the WhatsApp Business API cost guide.
The number: the decision that is hard to undo
Meta's phone number rules are short: the number must be yours, include a country and area code, and be able to receive a voice call or SMS. Short codes are not supported. A landline works if it can take the verification call.
A number already on WhatsApp. This is where most projects stall. Under ordinary registration, a number already in use on WhatsApp cannot be registered until that account is deleted, and deleting it loses the app's chat history on that account. For many small businesses that number is the one customers already have saved, so the choice matters.
Coexistence is the alternative. Meta now supports onboarding an existing WhatsApp Business app number through Embedded Signup, so the same number works on the app and on Cloud API. It needs app version 2.24.17 or higher and a partner registered as a Solution Partner or Tech Provider. The trade-offs are real: throughput is fixed at 20 messages per second, group chats are not synced, broadcast lists are disabled, linked companion devices are unlinked, and calls are not supported on Cloud API. Messages sent from the app also do not open or extend a Cloud API customer service window.
The rule of thumb. If you expect volume or automation, a dedicated number is cleaner. If the number on your shop window is the asset and your team still replies by hand, coexistence is the realistic path.
The activation sequence
- Confirm the portfolio and give admin access to whoever runs the setup, including your provider if you use one.
- Create the WhatsApp Business account directly or through Embedded Signup.
- Register the number with its display name. It must show as connected before it can send or receive through the API.
- Add the payment method on the messaging account.
- Submit the first templates. Anything you start yourself outside a customer service window has to be an approved template, so write the two or three you need first: see how template messages work.
- Start business verification in parallel rather than waiting for a problem. In Italy, expect to provide company documents such as a visura camerale; the exact list is the one Meta shows in your portfolio.
- Send a real test to a consenting internal number, reply from the customer side, and check that the conversation reaches the inbox where your team works.
Do not plan a launch around a promised number of days. We found no fixed review time published by Meta, so leave a margin before any date that matters.
Limits, verification and the display name
The first limit is 250. Meta's messaging limit is the number of unique recipients you can reach outside a customer service window in a moving 24-hour period. New portfolios start at 250, and the limit is shared by every number in the portfolio. Replies inside an open window do not count against it.
Two ways up to 2,000. You verify the business, or you deliver 2,000 messages outside customer service windows within 30 days using templates with a high quality rating. Verification is the faster route for a real company. Above 2,000, scaling to 10,000, 100,000 and unlimited is automatic if your quality is high and you used at least half of your current limit in the last 7 days.
The number cap moves too. A new portfolio can register two numbers. That rises to 20 once the business is verified or reaches a 2,000 limit, which matters if you run several shops or brands.
The display name is reviewed again as you grow. You provide it at registration, and Meta verifies it against its guidelines when you reach a higher limit. If it is rejected, the status becomes declined. You can change it up to 10 times in 30 days, and after an approved change you have 14 days to re-register the number.
Verification is not the green tick. Business verification proves the company exists. The green tick is a separate request with a separate bar, and you do not need it to send a single message.
Three checks before your first campaign
Consent you can prove. Activation gives you the technical ability to send, not the right to. Under GDPR and Meta's own rules you need an opt-in collected for this channel and a record of it. The Italian opt-in guide covers the wording.
A template with a real reason to exist. Quality rating reacts to user blocks and low read rates, and high quality is a condition for scaling. A cold promotional blast in week one is the most expensive way to discover this.
Someone who answers. A customer who replies opens a 24-hour window and expects a response. Decide who handles it, at what hours and with what escalation before you press send.
When the API is the wrong step
If one person replies to a few dozen customers a day and you have no integration to run, the free WhatsApp Business app does the job, and the API adds per-message costs, setup and governance you will not use. The same applies if you have no consented contacts yet: the channel cannot create the audience for you.
The API also will not fix a weak offer. If customers do not reply to your email or your calls, moving the same message to WhatsApp changes the cost before it changes the result. Start with the app, prove that people want to talk to you there, and move when you hit the limit of doing it by hand.
TikJoy runs on the official WhatsApp Business API and connects the number to an AI concierge, orders and cashback, so activation is not the end of the project but the start of a channel that answers. See how the WhatsApp AI Concierge works.