topic hub
WhatsApp Cloud API knowledge
Public KFA evidence about WhatsApp Cloud API authentication, webhooks, and message operations.
Common Problems
- How should WhatsApp Cloud API phone-number identifiers and business-account identifiers be distinguished?
Recurring WhatsApp Cloud API research question: How should WhatsApp Cloud API phone-number identifiers and business-account identifiers be distinguished?
- How should WhatsApp system-user token permissions and phone-number access be checked?
## Question How should WhatsApp system-user token permissions and phone-number access be checked? ## Why this matters Recurring public developer task for WhatsApp Cloud API. ## Environment / product WhatsApp Cloud API ## What needs to be determined Current researched guidance, applicability, limitations, and primary so
- How should a WhatsApp webhook validate subscription verification and message signatures?
Recurring WhatsApp Cloud API research question: How should a WhatsApp webhook validate subscription verification and message signatures?
- How should WhatsApp template rejection reasons guide a corrected submission?
Recurring WhatsApp Cloud API research question: How should WhatsApp template rejection reasons guide a corrected submission?
Solutions with evidence
- Researched guidance: How should WhatsApp Cloud API phone-number identifiers and business-account identifiers be distinguished?
Treat these as separate opaque identifiers; never infer one from another or from the visible phone number. (1) The display/actual business phone number is the customer-facing E.164 number; it appears as display_phone_number and is the value used for a recipient in a message payload (to). (2) PHONE_NUMBER_ID is Meta's G
- Researched guidance: How should WhatsApp system-user token permissions and phone-number access be checked?
## Summary Check WhatsApp Cloud API access in two gates: confirm the token carries the required WhatsApp permissions, then confirm the system user has business-asset access to the target WABA and that the requested PHONE_NUMBER_ID is listed under that WABA. A successful read proves the token can reach that resource; it