Send a direct message to one WhatsApp recipient. POST /{tenantId}/api/v1/sendDirectSendMessage/{whatsappNumber}.
Permissions
For API access tokens and OIDC tokens, satisfy at least one of: api, wati_integration:write, conversations:write. API access tokens may satisfy a listed scope through the configured scope hierarchy; OIDC tokens are checked against their scope claims. Legacy JWT authentication does not use this scope check. Authentication, role, tenant, and applicable feature or plan checks still apply. For HTTP 403, check the credential type, applicable scopes, roles, and workspace access; 403 does not always mean a missing scope. Authentication/authorization failures do not guarantee a JSON response body.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Invalid or missing request body, invalid direct-send fields or localMessageId, offline mode, direct-send feature unavailable, or send failure. The response body depends on the failure: offline mode can return a string; validation and send failures return an object with result=false and info.
Authorization failed. Check the Permissions section for the credential-specific scope rules, and check roles and workspace access. The response may have no body; do not require a JSON error envelope.