WhatsApp Business API Setup: The Approval Process Explained

Getting access to the WhatsApp Business API is more involved than most business APIs. There’s no “sign up and get an API key” experience — it requires a verified Meta Business account, a WhatsApp Business Account (WABA), a registered phone number, and Meta’s approval at multiple stages. The process isn’t technically complex, but it has several sequential steps and approval windows that take time. Understanding what’s involved before you start avoids the frustration of realising mid-setup that you need something you don’t have yet. This guide explains every step of the WhatsApp Business API setup process for UK businesses.

What you need before you start

Before beginning the WhatsApp Business API setup, you need:

A Meta Business account. If your business already advertises on Facebook or Instagram, you likely already have a Meta Business account (formerly Facebook Business Manager). If not, create one at business.facebook.com. You’ll need a personal Facebook account to create it.

A business website. Meta requires a website to verify your business. The website should clearly identify your business name, describe what you do, and include contact information. A bare-minimum placeholder site won’t pass verification.

A phone number not currently used with WhatsApp. The number you register for the API cannot be an active number on the personal WhatsApp app or the WhatsApp Business app. If you want to use a number currently used with the app, it must be migrated (which involves removing it from the app first). Many businesses use a new SIM or a VoIP number specifically for the API.

The ability to receive calls or SMS to that number. During setup, Meta verifies the phone number by sending a code via SMS or voice call. You need to be able to receive this code on the number you’re registering.

Step 1: Meta Business Verification

Meta Business Verification confirms that your Meta Business account represents a real, legitimate business. Without verification, your WhatsApp Business Account will have limited capabilities and messaging restrictions.

Verification is done in Meta Business Manager under Business Settings → Security Centre. Meta asks for:

Your legal business name exactly as it appears on official documents. Your business address. Your business phone number. Documents confirming your business identity — typically a Companies House registration document, a VAT certificate, a utility bill in the business name, or a bank statement. The accepted document types vary and Meta is sometimes specific about format and recency.

Verification typically takes 1–5 business days. Meta may request additional documentation if the initial submission is insufficient. Common rejection reasons: business name mismatch between the Meta account and the document, documents that are too old, or documents that don’t clearly show the business name and address together. Submitting clean, current documents the first time avoids the most common delays.

Step 2: Create a Meta Developer App

Go to developers.facebook.com and create a new app. Select “Business” as the app type. Link the app to your verified Meta Business account. Add the WhatsApp product to your app from the products list.

At this stage, you’ll have access to the WhatsApp API in test mode. Test mode allows you to send messages to up to 5 verified test numbers — useful for development and testing before going through the full production setup.

Step 3: Create a WhatsApp Business Account (WABA)

A WhatsApp Business Account is the container that holds your phone numbers, message templates and business profile within Meta’s WhatsApp infrastructure. Create it through your Meta Developer App under the WhatsApp product settings.

The WABA requires your business display name — this is what customers see as the sender name in WhatsApp. Meta reviews display names to ensure they accurately represent the business and don’t violate their naming policies. Overly generic names (“Customer Service”) or names that don’t clearly identify your business may be rejected.

Step 4: Register your phone number

Add the phone number you want to use for the WhatsApp API to your WABA. Meta verifies the number by sending a 6-digit code via SMS or voice call. Enter the code to complete number registration.

Once registered, the number is associated with your WABA and cannot be used simultaneously with the WhatsApp Business app or personal WhatsApp. A registered number has a “quality rating” that starts at high and changes based on customer feedback (blocks, reports). Maintain a high quality rating by sending relevant, opted-in messages only.

Step 5: Submit message templates

Before sending any outbound messages to customers who haven’t initiated a conversation, you need approved templates. Create templates in Meta Business Manager under WhatsApp Manager → Message Templates.

Each template needs a name, category (utility, marketing, or authentication), language, and body text with optional header, footer and buttons. Variable placeholders use double curly brackets: {{1}}, {{2}} etc. Keep template body text clear and relevant — vague or promotional-sounding utility templates are more likely to be rejected.

Utility and authentication templates typically approve within minutes to a few hours. Marketing templates face stricter review and take longer, sometimes requiring revision. Rejection reasons are provided by Meta — address them specifically and resubmit.

Step 6: Generate a system user access token

For production integrations, use a system user access token rather than a user access token tied to an individual person’s Facebook account. System users are created in Meta Business Manager and can generate access tokens that don’t expire (unlike user tokens, which expire every 60 days).

Create a system user in Meta Business Manager → Users → System Users. Assign the system user to your app and your WhatsApp Business Account with the appropriate permissions. Generate a token for the system user — this is the token used in your integration’s API calls.

Step 7: Configure webhooks

Webhooks are how Meta delivers inbound messages, delivery status updates and message reactions to your server. Configure the webhook URL in your Meta Developer App under the WhatsApp product settings. Meta sends a challenge request to your webhook URL to verify it — your endpoint must respond correctly to this challenge before Meta will start delivering events.

Subscribe to the webhook fields you need: messages (for inbound messages and status updates), message_reactions, and any other fields your integration uses.

How long the full setup takes

From start to first message sent in production: typically 1–3 weeks. Meta Business Verification is usually the longest step at 1–5 days. Template approval adds another few hours to a day. Number registration and webhook setup are fast once verification is complete. Development happens in parallel using the test environment, so the technical build doesn’t need to wait for every approval step to complete.

For the full service details, see the WhatsApp Business API integration service. For what the integration costs once access is in place, see WhatsApp Business API integration cost. For the complete API guide, see WhatsApp Business API integration guide. For how WhatsApp compares with SMS, see WhatsApp vs SMS for business messaging.

Common setup mistakes to avoid

Using a number that’s already on WhatsApp. The most common early mistake. If you try to register a number that’s active on the personal WhatsApp app or WhatsApp Business app, the registration will fail. The number must be removed from the app before registering it with the API. This means losing the message history on that number and any contacts who have saved it for WhatsApp conversations. Many businesses use a fresh number specifically for the API to avoid this entirely.

Mismatch between Meta Business name and legal documents. Meta’s verification checks that the business name on your account matches the name on the documents you submit. “Paul Walsh Web Design” on the Meta account and “Paul Walsh Web Design Ltd” on the Companies House registration will cause a mismatch. Use the exact legal name as it appears on your business registration documents.

Vague template content. Meta rejects templates that are too generic, look promotional despite being categorised as utility, or include placeholder text like “[INSERT DATE]” instead of proper variable syntax. Write templates as if sending them to a real customer — clear, specific, and with proper {{1}} variable formatting. Submit one template at a time initially to understand how Meta responds before submitting a full batch.

Not setting up a system user token. Many tutorials use a personal user access token for initial testing. Personal tokens expire every 60 days and are tied to an individual’s Facebook account — if that person leaves the business, the integration breaks. Use a system user token from the start for any production integration.

Ongoing account management

Once the WhatsApp Business API is live, several ongoing management tasks keep the integration running reliably. Phone number quality rating needs monitoring — if customers block or report your number, Meta reduces your messaging throughput. High quality ratings are maintained by sending only relevant, expected messages to opted-in contacts. Template usage metrics are available in Meta Business Manager and show which templates have high read rates and which might benefit from revision. Meta updates its API periodically — subscribing to Meta’s developer changelog means you get advance notice of changes that might require integration updates.

If you need help with a custom API integration for your website or business application, I can help. I build bespoke API integrations for UK businesses. See API integration pricing or get in touch to discuss your project.

Need a custom integration built?

I build custom API integrations — Stripe, Companies House and bespoke data pipelines. Reliable, well-documented, no agency overhead.

Discuss your project →