text
object
Sends a message to a conversation
code, not the text. To act before this happens, check active and chatWindowRemainingTime on the conversation, or subscribe to the subscription.service_window.expiring and .closed webhook events.
unified.media.url must be reachable when you call this endpoint. We download the file straight away and host our own copy, so short-lived pre-signed URLs are fine. We check the file type with a HEAD request, falling back to a one-byte GET for URLs that only allow GET, such as S3 and GCS pre-signed URLs. The Content-Type must be one WhatsApp supports.
body and header take a list for positional ({{1}}) templates, or an object keyed by variable name for named templates. An image header takes { "link": "https://..." }.buttons is only needed when the template has a dynamic button (a URL with a variable, or a flow). Then pass one value per button, in order. Values for static buttons, such as quick replies, are ignored. Templates with only static buttons can leave buttons out."emoji": null or leave it out to remove the reaction. Reactions follow the same 24-hour rule as other non-template messages. Customer reactions arrive as the message.reaction.updated webhook event.
replyTo with the message’s Wassist ID. This is the same message.id you get on message.received webhook events. It works on text and unified messages:
replyTo set. Errors:
Idempotency-Key header (any unique string up to 255 characters, such as a UUID) to make retries safe. Keys are scoped to your API key and kept for 24 hours.
POST /api/v1/conversations/ supports the same header.Unified input for sending text, template, or CTA URL messages.