> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp Business API Explained (And the Verification Myth)

> What the API actually is, and why you can start messaging real customers without verifying your business — untangles the four different 'verifications' Meta shows in its dashboard (app review, business verification, phone number verification, display name approval) and which one actually matters.

<Frame>
  <iframe className="w-full aspect-video rounded-xl" src="https://www.youtube.com/embed/vjxx2sjnCas" title="Use the WhatsApp API without business verification" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />
</Frame>

**Yes — you can start using the WhatsApp Cloud API and message real customers without verifying
your business.** No documents, no waiting on anyone's approval.

## Why people get confused

Meta's dashboard shows several different verification statuses at once — in the developer app,
in the business portfolio, on the WhatsApp account, and on the phone number itself. Because they
all appear together, it's easy to assume every single one is mandatory before you can send a
message. In reality, they're four separate processes with four separate purposes, and only one
of them is actually required to get started.

## The four things people confuse

<Steps>
  <Step title="Phone number verification">
    The **only** step actually required to start. Add your phone number, receive an OTP, and
    verify it — exactly like verifying a number on regular WhatsApp. Once verified, the number
    becomes available for Cloud API messaging.
  </Step>

  <Step title="Business verification">
    *Optional* until you want to scale past 250 unique customers a day. It also doesn't require
    an actual registered company — verifying as an individual with a minimal personal document
    (in India, a PAN card, GST, or Udyam number; Meta specifies the equivalent for other
    countries) is enough.
  </Step>

  <Step title="App review">
    *Optional* for normal use with your own number — you only need to submit a privacy policy
    and flip the app to **Live** mode, which Meta doesn't actually check. **App review only
    matters if you're an agency onboarding *other people's* numbers** through embedded signup
    (the "click a button, connect via a Facebook form" flow) — that's the one case where Meta
    reviews the app before you can onboard someone else.
  </Step>

  <Step title="Display name approval">
    Only relevant for Cloud API (see below) — e.g. `ChatSyncs`, `Rahul Electronics`,
    `ABC Pvt Ltd`. Meta reviews this name before it's shown to customers.
  </Step>
</Steps>

### What you actually need

If you're automating your own number, the checklist is short:

* ✅ **Phone number verification** — required.
* ⬜ Business verification — not required to start.
* ⬜ App review — not required to start.
* ⬜ Display name approval — not required to start.

The other three become relevant later — as you scale volume, onboard other businesses, or move
to Cloud API — but none of them block you from messaging real customers today.

<Note>
  So the honest answer: verify your **phone number**, and you can message real customers
  today — no documents, no waiting on approvals.
</Note>

## The number you have to respect

| Stage                        | Daily reach                                               |
| ---------------------------- | --------------------------------------------------------- |
| Before business verification | **250 unique customers / 24 hours**                       |
| After business verification  | **1,000 unique customers / 24 hours**                     |
| Then                         | Scales up automatically with volume + good quality rating |

That cap is on **unique people reached** in 24 hours — not total messages. You can exchange
unlimited messages with each of those people. For the full API-level picture, see
[Messaging limits & quality rating](/meta-api/concepts/messaging-limits-and-quality-rating).

<Note>
  Meta periodically updates messaging limits — always check the latest Meta documentation for the
  current numbers rather than treating any figure here as permanent.
</Note>

<Warning>
  Reaching your daily limit doesn't mean you should message all of them with marketing content
  just because you can. Sending to everyone regardless of opt-in or engagement is how quality
  ratings — and accounts — get restricted. See
  [WhatsApp Rules: How to Never Get Banned](/learn/whatsapp-rules-basics) before running any
  broadcast.
</Warning>

## Best practices even while you're not verified

Just because you *can* message up to your daily limit doesn't mean you should message everyone
on it right away:

* Send only to opted-in users.
* Segment your audience instead of blasting every contact the same message.
* Respect opt-outs immediately.
* Monitor your quality rating.
* Increase messaging volume gradually rather than jumping straight to full daily capacity.

Poor engagement or spam reports reduce account quality and can lead to messaging restrictions —
see [WhatsApp Rules: How to Never Get Banned](/learn/whatsapp-rules-basics) for the full picture.

## Cloud API vs coexistence

* **Cloud API** — your number is *not* on any WhatsApp app; ChatSyncs/Meta handles it
  entirely. Here a **display name** must be approved.
* **Coexistence** — you keep using the WhatsApp Business app on the phone *and* the API; the
  app's existing display name is used, so no separate approval.

<Tip>
  A Cloud API display name can get rejected if it's already in use elsewhere — e.g. a name that
  matches another business already registered with a similar service. Pick something distinct to
  your own business rather than a generic brand-style name.
</Tip>

<Warning>
  The free test number Meta gives you is temporary (\~90 days) and **cannot** be used in
  production. Add your own real number before you build anything that matters.
</Warning>

## Three mistakes that get beginners stuck

1. **"Number already registered to WhatsApp"** — delete WhatsApp from that number first,
   wait, then register it on the API.
2. **Payment fails / templates won't send** — use a Visa or Mastercard with international
   transactions on, and add your **Tax ID** in Business Info billing (templates stay blocked
   until you do, even after the card itself works).
3. **Webhook not working** — you must both return the `hub.challenge` response *and*
   subscribe to the messaging event. They're two separate steps people skip.

<Tip>
  Don't chase the green/blue tick. The green tick is no longer issued, and the blue
  (Official Business Account) badge isn't something you can apply for upfront — Meta watches
  message volume and quality over time and, once an account is eligible, sends a notification
  inviting you to request it. Focus on message quality and consistent, wanted volume; the badge
  follows on its own.
</Tip>

## Frequently asked

<AccordionGroup>
  <Accordion title="Do I need to verify my business before I can message customers?">
    No. Phone number verification is the only requirement to start messaging real customers.
    Business verification only raises your daily unique-customer limit — it doesn't gate access.
  </Accordion>

  <Accordion title="Do I need to submit my app for review?">
    Only if you're an agency onboarding *other businesses'* WhatsApp numbers through embedded
    signup. For your own number, just add a privacy policy and switch the app to Live mode.
  </Accordion>

  <Accordion title="Is 250 messages per day the real limit before business verification?">
    No — it's 250 *unique customers* reached per 24 hours, not 250 total messages. You can send
    unlimited messages within each of those conversations.
  </Accordion>

  <Accordion title="Why do I need a business document to verify, even without a registered company?">
    Meta accepts minimal personal documents (e.g. a PAN card in India) for individual
    verification — you don't need GST or a formally registered business to complete it.
  </Accordion>

  <Accordion title="Why isn't my display name getting approved?">
    A common cause is the name already being in use by another business or provider. Pick a
    name distinct to your own business rather than a shared or generic one. This only applies to
    Cloud API — Coexistence reuses your WhatsApp Business app's existing display name.
  </Accordion>

  <Accordion title="How do I get the blue verified badge?">
    You can't apply for it directly — Meta reaches out once an account is eligible based on
    sustained message quality and volume. Focus on that instead of chasing the badge itself.
  </Accordion>
</AccordionGroup>

## Summary

For businesses using their own WhatsApp number:

* **Phone number verification** is required.
* **Business verification** is optional when starting — it only raises your daily limit.
* **App review** is usually unnecessary unless you're onboarding other businesses' numbers.
* **Display name approval** is a separate process, and only relevant for Cloud API.

You can begin testing — and even message real customers — before completing every Meta
verification, but follow WhatsApp's messaging policies and scale your usage gradually to keep
the account healthy.

## What's next

Now set up the Meta side end-to-end — business portfolio, number, and permanent access —
in the [Meta account setup lesson](/learn/meta-account-setup).