How to Get WhatsApp Business API — The 2026 Application & Onboarding Guide

1. Who can apply for WhatsApp Business API in 2026

WhatsApp Business API is open to almost every legitimate business, but Meta gates access on three things: your business must be legally registered, your use case has to fall inside Meta's Commerce and Business policies, and the phone number you plan to use must not currently be active on WhatsApp's consumer app. If all three are true, you can apply.

Who gets through easily

• Registered private or public limited companies in India (Companies Act), the UAE (DED / free-zone licences), and most countries with an equivalent registry.
• Partnerships and LLPs with current registration certificates and a verifiable business address.
• Sole proprietorships and freelancers operating under a registered trade name — usually via a GST certificate, shop-establishment licence, or equivalent.
• Educational institutions, hospitals, travel agencies, retailers, restaurants, real-estate firms — all standard use cases for which Meta has approved thousands of accounts.

Who has to work harder to get approved

• Businesses in Meta's restricted categories — alcohol, tobacco, adult content, firearms, gambling, cryptocurrency, pharmacies, medical devices, and a handful of regulated finance categories. Some are allowed with restrictions; some are not allowed at all. Check Meta's current Commerce Policy before spending onboarding effort.
• Businesses without a registered legal entity — Meta Business Verification needs at least one government or bank document tying the business name to a verifiable record.
• Businesses using personal phone numbers currently active on WhatsApp — the number has to be deleted from WhatsApp (inside the consumer app) before it can be onboarded to the API, or you need to use a dedicated number.

2. WhatsApp Business API vs the free WhatsApp Business app

A surprising number of first-time applicants confuse the two. The distinction matters because it determines which number you can use and what you can do with it.

The rule is simple: if your business has more than one person answering WhatsApp messages, or if you need broadcasts, automations, integrations, or a green tick — you need the Business API. If you are a one-person business with under a few hundred messages a week, the free app is enough.

3. Cloud API direct vs going through a BSP

Meta ships the WhatsApp Business API two ways in 2026:

Cloud API direct

Meta hosts the API and you call it directly. You manage the phone number, send templates via Meta's endpoints, handle webhooks yourself, and bill Meta for conversations. It is free to use the Cloud API itself — you only pay Meta for conversations. The catch: there is no shared inbox, no campaign builder, no template manager, no AI layer, no integrations — just an HTTP API. Every operational feature is your developer team's problem.

BSP (Business Solution Provider) path

A BSP — Go4whatsup, WATI, Gupshup, Twilio, and dozens of others — is a Meta-approved partner that sits on top of Cloud API and ships a full product: inbox, broadcast, flow builder, CRM integrations, AI, reports, plus the onboarding paperwork. You still pay Meta for conversations (at exact cost, passed through), plus a platform fee to the BSP. For 90% of businesses this is the right path: you get a working product on day one instead of a six-month engineering build.

Go4whatsup is a Meta Business Partner and a registered BSP. The onboarding described in the rest of this guide is the BSP path, which is the path most readers should follow. The Cloud-API-direct path has a similar sequence but you do every step yourself without a named onboarding owner. For comparison of the two paths with honest trade-offs, see our Why Go4whatsup page.

4. Your pre-application checklist

Onboarding delays are almost always pre-application problems that surface when Meta reviews documents. Get these items in order first and the rest of the journey runs cleanly.

5. The seven-step onboarding journey

End-to-end, the path looks like this:

1. Day 0

   Confirm eligibility and assemble documents

   Walk the pre-application checklist. If anything is missing — most commonly an email on your own domain or a matching business name — sort it before starting the application. This alone saves most teams 2 to 3 days.

2. Day 1

   Create / verify your Meta Business Manager

   Sign in at business.facebook.com. Create a Business if you do not have one. Add an admin email (on your domain). Connect your Facebook Page — you will need one linked. This takes about 15 minutes.

3. Day 1–2

   Start Business Verification

   In Business Manager → Security Centre → Business Verification. Upload your registration certificate, enter your legal name exactly as it appears on the document, your address, and your business website. Submit. Meta's automated layer often approves in hours; a manual review takes 2 to 4 business days. See Section 7.

4. Day 2

   Pick your BSP and create your WABA

   If you are going the Go4whatsup path, we open the Embedded Signup flow in your browser — you click "Continue", grant the WhatsApp asset to Go4whatsup, and your WABA is created inside Meta. This takes about 5 minutes once Business Verification is submitted.

5. Day 2

   Add the phone number and complete OTP

   Enter the dedicated phone number. Meta sends an OTP via SMS (or voice call). Enter it. Set a 6-digit two-step verification PIN (you'll need this for future security operations). Number is live on the API — see Section 9.

6. Day 2–3

   Submit display name

   File your display name in Meta Business Manager → WhatsApp Manager. Typical turnaround is same-day to 24 hours. Rejected names are the #1 cause of onboarding delay — see Section 10 for the rules.

7. Day 3–4

   Submit first templates and send your first message

   Upload 3 to 5 message templates through Go4whatsup's template manager. Meta reviews — category rules matter. Most templates approve in 2 to 12 hours. Send your first test message to yourself or an opted-in colleague. You are live.

6. Meta Business Manager setup

Meta Business Manager (business.facebook.com) is the root of everything — your WABA, your Facebook Page, your Instagram business account, and your ad accounts all sit under a single Business. If you already run Facebook or Instagram Ads, you have one; reuse it. Do not create a new Business Manager just for WhatsApp — it creates verification friction.

Fields you'll be asked for

• Business name. Use your legal name (the one on your registration certificate), not a trading alias.
• Business email. On your own domain. This becomes your admin contact for the entire WhatsApp asset — treat it as permanent.
• Country, address, phone number. Self-explanatory, but all three must match your verification documents.
• Business vertical. Pick the closest match from Meta's list — the verification reviewer will cross-check this against your website content.

Assign the right admins

Add at least two admins to the Business Manager — one primary owner plus a backup. If the primary owner leaves the company, recovery is painful without a backup admin still on file. Both admins should use email addresses on your company domain.

7. Business Verification explained

Business Verification is the gate. It is not the same as WhatsApp green-tick (OBA) verification — green tick is a separate filing that comes later, covered in our Green Tick guide. Business Verification is the more basic check: Meta is asking "is this a real, legally registered business?" and needs one acceptable document to confirm it.

Documents Meta accepts (India)

• Certificate of Incorporation (Companies Act)
• GST Registration Certificate
• Shop and Establishment Licence
• Partnership Deed (for partnerships, with registration receipt)
• MSME Udyam registration certificate

Documents Meta accepts (UAE)

• DED trade licence (mainland Dubai / any emirate)
• Free Zone trade licence (DMCC, JAFZA, DAFZA, RAKEZ, etc.)
• Chamber of Commerce certificate
• Commercial Registration Certificate (CR)

What actually gets rejected

8. Creating your WhatsApp Business Account (WABA)

A WABA is the Meta-side record that holds your phone numbers, templates, and messaging rights. One business can have multiple WABAs — typically one per brand or per country — and one WABA can hold multiple phone numbers. Most first-time applicants start with one WABA and one phone number.

What happens during WABA creation

On the Go4whatsup path, we open Meta's Embedded Signup flow — a standard OAuth-style consent screen from Meta. You see the permissions Go4whatsup is asking for (manage WhatsApp assets on your behalf, read templates, send messages) and click "Continue". Meta creates the WABA inside your Business Manager and grants Go4whatsup the agency role. This is the same flow every Meta-approved BSP uses — Meta validates each BSP's embedded flow directly.

What you're agreeing to

• Go4whatsup can send messages from your numbers using your templates.
• Go4whatsup can manage templates — submit new ones, edit, delete.
• Go4whatsup can read webhooks — inbound messages route through our platform.
• Your business retains ownership of the WABA itself — you can remove Go4whatsup's agency access at any time from Business Manager, and move to a different BSP via a BSP transfer without losing your number (see our WATI migration guide for how a BSP transfer works in practice).

9. Phone number onboarding and two-step verification

The phone number is where most of the rules live. In 2026 the rules are well-settled and breaking them is the #2 cause of onboarding friction after Business Verification.

Phone number rules

The two-step verification PIN

After OTP confirms the number, Meta asks for a 6-digit two-step verification PIN. This is a security layer, not a login — it's required whenever the phone number is migrated to a new WABA, re-verified, or moved between BSPs. Store this PIN somewhere your ops team can retrieve it: a password manager, a vault, or a sealed document in your admin's drawer. If you lose this PIN, the number is difficult to recover — Meta requires a 7-day waiting period to reset it, during which the number cannot send.

10. Display name review — the most common rejection cause

Your display name is the name recipients see above your messages when they don't have your number saved. Meta reviews each display name manually against an evolving set of rules, and this step rejects more first-time applications than any other.

Rules Meta applies

• Must be your business brand or a recognisable variant. Exact match to your legal name is not required — but the name must clearly identify your business.
• Cannot be generic. "Support", "Sales", "Info", "Customer Care", "Contact Us" — all automatic rejections.
• Cannot include promotional language. "Best Deals", "Sale", "Offers", "Cheapest" — rejected.
• Cannot misrepresent the business. If your registered name is a retailer, you cannot use a display name that implies you're a bank or a government service.
• Must be between 3 and 512 characters and use standard Latin / local script characters — no emojis, no unusual Unicode.
• No URL or phone number in the name. "go4whatsup.com" as a display name is rejected.

Display names that work

• Your brand name, as it appears in your marketing: Go4whatsup, Urban Thread Retail, Al Rawan Travel.
• Your brand name plus a regional qualifier, when justified: Al Rawan Travel UAE.
• Your brand name plus a specific sub-service, when your trade licence covers it: Saanvi Crafts — Wholesale.

Display names that get rejected

• Customer Support — generic.
• Best WhatsApp Deals — promotional.
• 🎉 Go4whatsup 🎉 — emojis not allowed.
• Info — generic, too short.
• +91 96675 84436 — phone number not allowed as display name.

11. Submitting your first message templates

A template is a pre-approved message format — header, body, footer, and optional buttons — that you're allowed to send outside the 24-hour session window. Every new WABA has to submit its first templates and get them approved before sending anything meaningful. Meta reviews each template against content policy and category rules.

The three template categories

• Marketing. Promotional, sales, re-engagement, newsletter. Highest scrutiny; rejection rate is the highest of the three.
• Utility. Transactional notifications the customer is expecting — order confirmation, shipping update, payment receipt, appointment reminder. Usually approved quickly.
• Authentication. OTP and verification codes only. Must use Meta's authentication template format — no free-text.

Starter templates we recommend for onboarding

1. Welcome message (Utility) — "Hi {{1}}, welcome to {{2}}. Reply anytime to chat with us."
2. Order confirmation (Utility) — "Hi {{1}}, your order #{{2}} for {{3}} has been confirmed. Estimated delivery: {{4}}."
3. Appointment reminder (Utility) — "Hi {{1}}, this is a reminder for your appointment at {{2}} on {{3}}."
4. OTP (Authentication) — standard authentication template with the OTP variable.
5. Promotional offer (Marketing) — introductory campaign; tag category as Marketing and include an opt-out note.

12. Messaging-limit tiers and the first 90 days

New WhatsApp numbers do not start with unlimited sending. Meta uses a tiered messaging limit that expands as your number demonstrates quality. Understanding this protects your first campaigns from being rate-limited.

The limits apply to unique new conversations, not total messages. A reply back to a customer who already messaged you does not count against the tier. This is why most small teams never bump into the tier limit — their broadcast lists are smaller than 250 unique recipients anyway.

How to climb tiers quickly without getting penalised

• Start with Utility templates. They earn quality and volume without triggering marketing-message spam flags.
• Segment aggressively. Send only to recipients who recently engaged or recently opted in. Cold lists tank your quality rating and roll you back to Tier 1.
• Watch block and report rate. If your number hits ≥2% block rate or ≥1 report per 1,000 messages, Meta drops your quality rating to "medium" or "low" and freezes tier advancement.
• Avoid message-burst patterns. Instead of 10,000 messages in 10 minutes, pace over 4 to 8 hours. Go4whatsup's broadcast pacing is on by default and can be configured per campaign.

13. Common rejection reasons (and how to fix them)

Here is the rejection-reason list we see most often, with the fix for each.

14. Typical timelines — India, UAE, global

These are ranges we see for standard onboardings with documents in order. Edge cases — restricted categories, cross-border businesses, very new entities — take longer.

India and UAE timelines are broadly similar in 2026 — Meta reviews are no longer market-differentiated for standard categories. What changes between markets is the document list (GST vs DED) and the time zone of the review team; a submission at 10am IST typically gets a first-pass response faster than one at 3am IST.

15. How Go4whatsup runs onboarding

For PRO and Enterprise customers, Go4whatsup's onboarding is a named-owner process with a fixed first-milestone commitment: