POST /api/v1/messages/send

Request contract

• Required scope is messages:send.
• to accepts one nonempty string, a comma-separated string, or a nonempty string array. Parsed recipients are deduplicated and limited to 50.
• type is text or template and defaults to text. text.body is required for text; template is required for template sends.
• Template can identify id, name, language, and string-to-string variables. sender_phone_number_id and client_reference are optional.

Example request

curl -X POST "/api/v1/messages/send" \
  -H "Authorization: Bearer tus_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"to":"+919876543210","type":"text","text":{"body":"Hello"},"client_reference":"order-123"}'

Response contract

{
  "request_id": "msgreq_example",
  "account_id": "account_uuid",
  "client_reference": "order-123",
  "type": "text",
  "accepted_count": 1,
  "failed_count": 0,
  "results": [{ "to": "+919876543210", "status": "accepted", "message_id": "wamid.example" }]
}

A mixed or wholly failed recipient batch can still return the aggregate response. Inspect every results entry. Accepted means the provider request succeeded at that stage; it does not prove delivery.

Recover send failures

• Correct recipient E.164 formatting and WhatsApp availability.
• Use free-form text only inside an eligible 24-hour customer-service window.
• Choose an approved account template associated with the selected sender and complete variables.
• Resolve consent, sender, template, rate_limited, or provider errors before a deliberate new attempt.