What is a WhatsApp ID (wa_id)? Meaning and example

What a WhatsApp ID is

A WhatsApp ID is how the WhatsApp Business Platform identifies the person on the other side of a chat. When a customer messages your business, your webhook receives their WhatsApp ID in the wa_id field next to their profile name. When you send a message, Meta's response tells you which WhatsApp ID the number you typed was matched to.

For an ordinary WhatsApp user, the closest everyday equivalent is their phone number with the country code, written without the plus sign, spaces or dashes. That is also the format WhatsApp asks for in click-to-chat links such as https://wa.me/919812345678. But in the API the WhatsApp ID is its own field, and Meta's webhook reference says a user's ID and phone number "may not always match", so store the wa_id you receive instead of rebuilding it from the number.

WhatsApp ID example

Meera, a customer in Pune with the number +91 98123 45678, writes "Is the blue cushion cover back in stock?" to Rangoli Home. A trimmed version of the webhook Rangoli Home's system receives looks like this:

{
  "object": "whatsapp_business_account",
  "entry": [{
    "id": "102290129340398",
    "changes": [{
      "field": "messages",
      "value": {
        "messaging_product": "whatsapp",
        "metadata": {
          "display_phone_number": "919900011122",
          "phone_number_id": "106540352242922"
        },
        "contacts": [{ "profile": { "name": "Meera" }, "wa_id": "919812345678" }],
        "messages": [{ "from": "919812345678", "type": "text",
          "text": { "body": "Is the blue cushion cover back in stock?" } }]
      }
    }]
  }]
}

Three different IDs appear in that one payload, which is why they are so often confused:

When Rangoli Home replies, it sends to Meera's number in the to field and calls the endpoint of its own phone number ID. Meta's send response then lists the number as input and the matched wa_id, for example "input": "+919812345678", "wa_id": "919812345678". Meta recommends always including the plus sign and country code in to; without the plus sign the API may add the business's own country code and reach the wrong person.

Usernames and business-scoped user IDs

WhatsApp is rolling out usernames gradually in 2026. For a user who adopts a username, Meta also sends a business-scoped user ID (BSUID) in a user_id field, a value such as US.13491208655302741918 that is unique to your business portfolio. Meta's documentation says the phone number fields, including wa_id, can be left out for such a user unless, for example, you have exchanged messages or calls with that number in the last 30 days. Meta marks this area as subject to change, so code that assumes wa_id is always present should be updated to fall back to user_id.

Why the WhatsApp ID matters

• Matching chats to customers. Your CRM should key conversations on the ID WhatsApp sends, so that a reply, an order update and a support ticket all land on the same contact.
• Avoiding duplicates. The same person saved as 09812345678, +91 98123-45678 and 919812345678 becomes three contacts unless you normalise to the WhatsApp ID.
• The 24-hour window. The customer service window is tracked per customer, so you need a reliable customer ID to know whether you may send a free-form reply or need a template.

WhatsApp ID in Broadchat

In a Broadchat panel you never handle wa_id by hand. Incoming messages are matched to a contact in CRM → Contact by the customer's number, and replies go out from the inbox without you typing any ID. Developers who add their own URL in a channel's Webhooks tab receive incoming messages and statuses in Meta's own payload format, so the wa_id, phone_number_id and account ID fields arrive exactly as shown above. Broadchat is built on the official WhatsApp Business Platform (Cloud API) and is not affiliated with or endorsed by Meta. For how these pieces fit together, start with what the WhatsApp Business API is.