Retained legacy exception: Request WhatsApp contact information, currently absent from V3 interactive sends.
Request WhatsApp contact information, currently absent from V3 interactive sends.
Provide target or whatsappNumber. This asks the recipient to share information; it does not silently retrieve a phone number. Availability depends on WhatsApp/Meta eligibility and account support. Delivery is asynchronous; use message-status webhooks. Do not automatically resend after an unknown outcome.
Permissions
For API access tokens and OIDC tokens, satisfy at least one of: api, wati_integration:write, conversations:write. Legacy JWTs do not use this scope check. Allowed roles: DEVELOPER, ADMINISTRATOR, EXTERNAL_ADMINISTRATOR, PARTNER_ADMINISTRATOR, AI_OPERATOR or API_TOKEN or TRIAL. FLEXI_TRIAL and FLEXI_PAID are denied even with another listed role. Workspace and billing restrictions also apply. WhatsApp and Meta/account eligibility, a valid customer-service session, and channel access are required.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
401Unauthorized; a JSON body is not guaranteed.
403Access denied by scopes, roles, workspace or billing; a JSON body is not guaranteed.
429Rate or usage limit exceeded.

