WhatsApp Cloud API overview
The five Meta objects you are about to create, how they fit together, and why there is no QR code.
Before you start clicking through Meta's tools, it helps to know what you are building. Almost every setup problem comes from confusing two of these five things.
The pieces
| Thing | What it is | You end up copying |
|---|---|---|
| Meta Business Manager | The container for your company's assets on Meta. | Business ID (optional) |
| Meta App | A developer app that holds the WhatsApp product. | — |
| WhatsApp Business Account (WABA) | The messaging account that owns your numbers, templates and quality rating. | WABA ID |
| Phone number | The actual number customers message. Lives inside the WABA. | Phone Number ID |
| System user + token | A non-human account whose token lets this app act for you. | Access token |
A useful mental model: the Business Manager owns the WABA, the WABA owns the phone number, and the system-user token is the key that lets us use them.
Phone Number ID is not your phone number
+260 97 123 4567 is your display number. The Phone Number ID is a ~15
digit identifier Meta assigns to it, like 109534567891234. They are different
values and the app needs the ID. Same trap with WABA ID vs Business ID.
Why there is no QR code
If you have used other WhatsApp tools you may expect to scan a QR code with your phone. That approach drives the normal WhatsApp app through an unofficial connection. It is quick to set up and it is fragile: numbers get banned, sessions drop, and it is against Meta's terms.
This platform uses the official Cloud API only. That means:
- Your number will not get banned for using automation — this is the sanctioned path.
- Messages are hosted by Meta, so nothing depends on a phone staying online.
- You get real infrastructure: message templates, quality ratings, delivery receipts, interactive Flows, a product catalog.
- The setup is longer, because Meta verifies who you are first.
The trade is a harder first hour for a connection that does not fall over.
Two rules that shape everything
The 24-hour service window
You can only send free-form messages to someone within 24 hours of their last message to you. Outside that window you must use a pre-approved template. This is a Meta rule, not ours — the inbox shows a countdown timer on each conversation so agents can see where they stand. Full detail in The 24-hour window and templates.
Messaging limits and quality
New numbers start limited (typically 250 business-initiated conversations per day) and step up as you send well-received messages. Getting blocked or reported pushes your quality rating down and can cut your limit. See Messaging limits and quality rating.
Next
Start building: Meta Business Manager.