WhatsApp Business API
WhatsApp Business API Registration: Step-by-Step Guide (2026)
How to register for the WhatsApp Business API: business verification, phone number setup, and generating your access token, step by step for 2026.
Summarise with AI
Short on time? Let AI do the work. Get the key points.
SHARE
WhatsApp Business API registration trips up more businesses than it should, not because the steps are hard, but because Meta splits them across three different tools: Meta for Developers, Business Manager, and WhatsApp Manager.
Unverified accounts are capped at 250 conversations per 24 hours, and business verification is what removes that cap. What people call an API key is really an access token, and there are two kinds depending on the stage you are at.
This guide walks through the five registration stages in order: creating a Meta app, verifying your business, registering your phone number, and generating the right kind of access token for production.
Table of Contents
What do you need before you start WhatsApp Business API registration?
You need three things before you touch a single setting: a Meta Business Manager account, a phone number that is not currently active on the regular WhatsApp or WhatsApp Business app, and legal documents that match your business’s registered name.
The phone number requirement catches people out the most. If a number is already logged into WhatsApp on a phone, you must migrate or delete that account first. Meta will not register a number that is actively serving personal or Business App traffic without an explicit migration step.
Your legal documents need to match exactly. The name on your tax ID, incorporation certificate, or business license must be identical to the legal entity name you enter in Business Manager, not a trading name or a shortened brand name. Mismatches are the single biggest cause of verification rejection.
How do you register for the WhatsApp Business API? A step-by-step walkthrough
Registration runs through five stages, and skipping the order causes most of the confusion people run into.
Create a Meta app. Go to Meta for Developers, create a new app, and choose “Business” as the app type. Add the WhatsApp product to that app from the dashboard.
Connect or create a WhatsApp Business Account (WABA). This is the container that holds your phone numbers, templates, and message logs, separate from the app itself.
Verify your business. Submit your legal documents through Business Manager. This step is what lifts you out of the 250-conversation cap described in Meta’s platform overview.
Register your business phone number. Add the number in WhatsApp Manager, verify ownership through an SMS or voice code, then call the registration endpoint to activate it for API traffic.
Generate an access token. A temporary token works for a first test message. Swap it for a permanent System User token before you build anything real.
Most guides stop at step 5 and call it done. In practice, the business verification step (stage 3) is what actually determines your timeline, since it is the only stage Meta cannot instantly automate.
If you would rather see this as one continuous walkthrough with screenshots, the full setup guide covers the same five stages end to end.
Where do you find the official WhatsApp Business API documentation?
The official WhatsApp Business API documentation lives entirely on developers.facebook.com, under the Business Messaging section, not on the general Facebook for Developers homepage.
Start at the Get Started page for the current onboarding flow, then branch out to the reference docs for the specific pieces you need: phone number registration, access tokens, and the embedded signup overview if you are integrating on behalf of other businesses rather than registering your own number.
Meta updates these pages more often than third-party tutorials do, including this one. When a specific setting does not match what you see on screen, the official docs are the tiebreaker, not a blog post from 2023.
How do you get your WhatsApp Business API key?
There is no single “API key.” What people call the API key is an access token, and you need two different kinds depending on the stage you are at.
Token type | Where you get it | Expires | Use for |
|---|---|---|---|
Temporary token | App dashboard, WhatsApp product setup screen | 24 hours | Sending your first test message |
Permanent System User token | Business Settings > System Users | Never, unless revoked | Production integrations, any live platform |
To generate the permanent version, go to Business Settings, open System Users, create a new system user, then assign it Full Control access to both your app and your WhatsApp Business Account. Click Generate token and store it somewhere secure immediately, since Meta shows it to you exactly once. Meta’s own access token guide and its authorization tokens explainer both walk through this same flow if you want the screen-by-screen version.
Never hardcode a permanent token into client-side code or a public repository. Treat it like a password, because functionally, it is one.
Why is there no WhatsApp Business API login page?
There is no login page because the API itself is not an application you sign into. It is a set of endpoints your app or platform calls using your access token as credentials.
What people are actually looking for when they search for a “login” is one of two things: Meta Business Suite (where you manage your business account, ad accounts, and pages) or WhatsApp Manager (where you manage phone numbers, templates, and quality ratings specifically for WhatsApp). Both sit inside Business Manager, reachable with your normal Facebook login.
If you are managing WhatsApp on behalf of a client business, embedded signup replaces the manual login flow entirely. The client authenticates once, and your app receives delegated access to their WhatsApp assets without ever seeing their Business Manager credentials.
Meta’s role in WhatsApp Business API registration
Meta is the platform owner. Every registration step, from business verification to phone number activation, happens inside Meta’s infrastructure, whether you use the API directly or go through a tech provider.
This matters because “WhatsApp Business API” and “Meta” are not competing options, they are the same underlying system described two ways. A tech provider or BSP (Business Solution Provider) does not replace Meta’s registration process. It sits on top of it, handling the automation, chatbot flows, and broadcast tooling that raw API calls do not give you out of the box.
Meta’s platform overview is the clearest single explanation of where Meta’s role ends and a tech provider’s role begins. If you are still deciding whether you even need the API layer versus the free consumer app, the app vs API comparison walks through that decision directly.
Business verification documents Meta asks for
Meta asks for a legal document proving your business name and address, plus a live website that displays that same legal name.
Accepted documents typically include a business license, articles of incorporation, or a business tax return, and the document must show your registered address or phone number matching what you entered in Business Manager. Meta’s own document upload guidance requires that scans be in color, uncropped, and fully legible, since a blurry photo is an instant resubmission.
Review takes 5 to 15 business days per cycle. If Meta rejects your first submission, fixing the issue and resubmitting restarts that same window rather than picking up where you left off, so getting the document right the first time matters more than getting it in fast. Our own document checklist breaks down exactly what to gather before you submit.
What causes WhatsApp Business API registration delays?
Most delays trace back to one of three mistakes: a name mismatch between your legal document and Business Manager, a phone number that is still active on a personal or Business App account, or a business website that does not display the exact legal entity name.
A trading name or shortened brand name on your document, when Business Manager has the full legal entity name (or vice versa), is the most common single rejection reason. Double-check this before you submit anything.
The second most common issue is trying to register a phone number that is still logged into WhatsApp somewhere. Meta will reject the registration call until that number is migrated away from personal use. If you already applied and got stuck, the step-by-step application guide covers the exact migration sequence.
A slower but real delay: businesses that submit incomplete document sets piecemeal, triggering multiple review cycles instead of one clean pass. Gather every required document before you submit once.
What happens after registration is approved?
Once you are verified and your number is registered, you can send template messages, receive and reply to customer conversations for free, and start building the automation your business actually needed the API for in the first place.
This is also the point where most businesses realize registration was the easy part. Raw API access gets you a phone number and a token, not conversation flows, broadcast segmentation, or a shared inbox for your support team. That is the layer a platform like Xobito adds on top of the same Meta-verified registration you just completed.
One thing to get right immediately after approval: message templates. Rejections are common, usually for promotional trigger words or missing opt-out language, and Meta reviews each submission individually. Before you send your first broadcast, it is worth reading why templates get rejected so you do not burn your first submission on an avoidable mistake.
Registration is a one-time hurdle. Getting your first templates approved and your first automation flow live is the part that actually determines whether the API pays for itself.