Skip to main content

WhatsApp Cloud API - Business Account API | Developer Documentation

Label each reference before using it

A number copied from an account screen may identify an account or an asset, rather than a telephone number. Keep the label and the screen where it appeared. This makes a support request useful without treating a Meta identifier as a ChatArchitect credential or message recipient.

ReferenceWhat to keep with itDo not substitute it for
Business portfolioIts readable name and an identifier, if available in the account you can access.A WhatsApp account, telephone number or API credential.
WhatsApp Business Account (WABA)The account name, identifier when available, and the selected portfolio.The telephone number used by a customer.
Meta phone-number asset IDIts exact label and the business number it refers to, if shown.The destination telephone number in a ChatArchitect send request.
Business telephone numberThe actual number and the connected tool or service.The recipient's number.
ChatArchitect App key/App IDA reference to the issued connection and credential storage.A Meta Business ID or WABA ID.
Message referenceThe system that issued it, the attempt, recipient and time.An account reference or a universal cross-system identifier.

Prepare a useful support record

  1. Start with the account-selection guide and record the intended portfolio, account and business number together.
  2. Copy available asset references as text with their labels; do not guess an identifier from a similar name or numeric length.
  3. Add the connected tool, the failed step and time with time zone. For a sending problem, include the available attempt reference and result.
  4. Remove passwords, Secret values, PINs and one-time codes from screenshots. If a requested reference is not visible, say so instead of creating a Meta token to retrieve it.

Use each reference in its own context

For API authentication, follow the ChatArchitect credential instructions. For a send recipient, follow the phone-format checklist. For application records, keep identifier strings and their issuing system together; similarly named fields in Meta, a CRM and ChatArchitect do not establish an interchangeable contract.

This guide does not require every customer to collect every Meta ID. It helps label the references available in the supported connection and ask for missing information.

No comments to display