WABA ID vs Phone Number ID vs Meta Business ID: What's the Difference?

WhatsApp Cloud API · Developer guide · 2026

WABA ID vs Phone Number ID vs Meta Business ID: What's the Difference?

Open your Meta setup and you'll see a Business ID, an App ID, a WABA ID, a Phone Number ID and your actual phone number. They're all long numbers, and they're not interchangeable. Put the wrong one in an API call and you get a vague error and an afternoon of debugging.

By On Cloud API team · Updated 27 September 2026

Quick answer

They nest like this, from biggest to smallest:

Business ID → WABA ID → Phone Number ID → messages

One business can have several WABAs, and one WABA can have several phone numbers. Each phone number has its own Phone Number ID.

All the Meta IDs compared

What is the Meta Business ID?

It's the ID of your Meta Business Portfolio, the container that owns your ad accounts, pages, apps and WhatsApp accounts. You'll also see it called Business Manager ID, BM ID or Facebook Business ID. Same thing.

For WhatsApp, its main API use is finding the WABAs your business owns:

GET https://graph.facebook.com/<GRAPH_API_VERSION>/<BUSINESS_ID>/owned_whatsapp_business_accounts
Authorization: Bearer <ACCESS_TOKEN>

WABAs that a client has shared with you (common for agencies) come from /<BUSINESS_ID>/client_whatsapp_business_accounts instead. Business-level calls like these need the business_management permission on your token.

What is a WABA ID?

WABA stands for WhatsApp Business Account. The WABA ID identifies that account. Your message templates, phone numbers and webhook subscription all hang off it. It's not your Business ID, not your App ID, not your phone number and not your token.

The two WABA calls you'll use most:

# List the phone numbers in this WhatsApp Business Account
GET /<WABA_ID>/phone_numbers

# Subscribe your app to this account's webhooks
POST /<WABA_ID>/subscribed_apps

Message templates also live at the WABA level (/<WABA_ID>/message_templates), not per phone number.

What is a WhatsApp Phone Number ID?

It's Meta's ID for one specific sender number. It's the value that goes in the URL when you send a message. It is not the phone number itself:

When you call /<WABA_ID>/phone_numbers, Meta returns both side by side, which makes the difference obvious:

{
  "data": [
    {
      "verified_name": "Your Business",
      "display_phone_number": "+92 300 1234567",
      "id": "123456789012345",
      "quality_rating": "GREEN"
    }
  ]
}

The id is your Phone Number ID. If you have a sales number and a support number, each has its own ID, so make sure your code sends from the right one.

Which ID goes in which WhatsApp API endpoint?

Bookmark this table. It answers most "which number goes here?" questions.

All endpoint URLs start with https://graph.facebook.com/<GRAPH_API_VERSION>/, and every call carries your access token in the header.

Here's a full send request, with both "numbers" in it:

curl -X POST \
"https://graph.facebook.com/<GRAPH_API_VERSION>/<PHONE_NUMBER_ID>/messages" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
  "messaging_product": "whatsapp",
  "to": "<CUSTOMER_NUMBER>",
  "type": "template",
  "template": { "name": "hello_world", "language": { "code": "en_US" } }
}'

PHONE_NUMBER_ID is your sender's Meta ID. to is the customer's phone number, in international format. Two different things.

Where to find your Business ID, WABA ID and Phone Number ID

If you connected through a Tech Provider using Embedded Signup, the provider receives your WABA ID and Phone Number ID automatically during onboarding.

Used the wrong ID? Errors and fixes

A wrong ID usually shows up as error 100 ("Invalid parameter" or "Unsupported get/post request") or a permissions error. Here are the common mix-ups:

Debug from the top down

1. Check the token in Meta's Access Token Debugger: is it valid, and does it have the WhatsApp permissions?
2. Call /WABA_ID/phone_numbers. If this works, your token and WABA ID are fine.
3. Copy the id of the exact number you want to send from, not display_phone_number.
4. Retry the send with that Phone Number ID.

Tools like n8n, CRMs and plugins label these fields differently: "Sender ID", "Business Account ID", "Phone ID". Map each field to the object it actually needs. Our WhatsApp Business API + n8n guide shows exactly which Meta value goes into each n8n field. For the bigger picture of how the Cloud API, WABA and numbers fit together, see our WhatsApp Cloud API overview.

These IDs work the same way whether your business is in Pakistan, the UAE, India, Bangladesh, the UK or the US. Meta assigns them; you never create them yourself.

Frequently asked questions