WhatsApp Business API requirements are shorter than most people expect — and longer than the marketing pages admit. There are five things you genuinely need before your first API message goes out: a Meta Business account, a WhatsApp Business Account, a phone number you can verify, an approved display name, and a platform to run the conversation on. Everything else is optional, negotiable, or a nice-to-have that sellers dress up as a requirement. Here is the honest checklist.
Requirement 1: A Meta Business account
The API lives inside Meta's business system, so you need a Meta Business account (formerly Business Manager) — the same account type that manages Facebook Pages and ad accounts. You do not need a public Facebook Page with followers, and you do not need to run ads; the account is the administrative shell that owns your WhatsApp assets. One person can create it in minutes, and it is free. If you already advertise on Meta, you already have one.
Requirement 2: A WhatsApp Business Account (WABA)
Inside the Meta Business account you create a WhatsApp Business Account — the container that holds your phone numbers, templates, and messaging limits. A WABA is not a phone number and not a profile; think of it as the folder. One business typically runs one WABA, and multiple numbers can live inside it. Creating it costs nothing, and it is where Meta applies your messaging limits and quality rating.
Requirement 3: A phone number you can verify
Every API number must be verified by SMS or voice call, so the number has to be able to receive a code. That rules out numbers you do not control and shared numbers you cannot verify. The number also cannot already be registered on WhatsApp — personal or Business app — at the moment you add it; an existing registration must be deleted first. A dedicated business number is the right call here, because the number becomes your public contact point and is painful to change later.
Requirement 4: An approved display name
The display name is what customers see instead of your number, and Meta approves it against rules: it must match your business, not be generic, and not mislead. This is the requirement people underestimate — a name like “Customer Service” or a brand you cannot document gets rejected, and a rejection stalls the whole setup. The full rules, and the rejection reasons to avoid, are in the
Requirement 5: A platform to run it on
The API is infrastructure, not an app — it sends and receives messages, but it does not give you an inbox, an AI agent, or templates to manage. You need a platform (or your own code) on top of it. On Neksio that means connecting your number, uploading your business documents, and letting the agent answer from them — Free gives 100 AI replies a month on WhatsApp, Starter $8.99 gives 5,000, Growth $11.99 gives 15,000 including Facebook and Instagram, and Scale $29.99. Meta's own per-message fees are billed separately by Meta.
What you do not need
- Business verification to start: you can test and send within initial limits before verification; verification raises limits and unlocks the green tick path, but it is not the first gate.
- A Facebook Page with followers: the Meta Business account is required, a public Page is not.
- A developer: no-code platforms connect the API without writing code.
- A new phone handset: the API number does not live on a phone at all — it lives in the cloud.
- A big budget: access itself is free from Meta; you pay per-message fees and your platform plan.
Documents to have ready
Have these on hand before you start, because verification — when you reach it — asks for them: your legal business name as registered, a business document that proves it (registration, licence, or tax document depending on your country), a website or public presence that matches the name, and a payment method for Meta's Billing Hub, so message delivery never pauses when a free tier runs out. Gathering these first turns a multi-week stop-start into one clean pass.
Owner: “I assumed I needed a Facebook Page and a developer.” Neither. A Meta Business account, a number, and a platform — that is the whole list.
The order that avoids rework
Create the Meta Business account, then the WABA, then add and verify the number, then submit the display name, then connect your platform. Doing verification early is smart if you plan to message at volume, but do not let it block your first test conversations — those work before verification completes. The step-by-step walkthrough is the
API access guide, and the timeline for each stage is covered in the approval time guide.
100 AI replies a month on WhatsApp, no credit card. Plans on the pricing page.
Frequently asked questions
- What are the WhatsApp Business API requirements?
- Five things: a Meta Business account, a WhatsApp Business Account, a phone number you can verify by SMS or voice call, an approved display name, and a platform to run conversations on. Access itself is free from Meta; per-message fees and your platform plan are the paid parts.
- Do I need business verification before I can use the API?
- No. You can test and send within initial limits before verification. Verification raises your messaging limits and is required for the green tick, but it is not the first gate — start, then verify.
- Do I need a Facebook Page to use the WhatsApp API?
- No. You need a Meta Business account, which is the administrative shell for WhatsApp assets. A public Facebook Page with followers is not required.
- Can I use my existing business phone number?
- Yes, if you can receive a verification code on it and it is not currently registered on WhatsApp. If it is registered on the personal or Business app, delete that registration first — and note that the app stops working on that number once it moves to the API.
- Do I need a developer to set up the WhatsApp API?
- Not with a no-code platform. The API itself is infrastructure; a platform like Neksio provides the inbox, agent, and template management without code.
