Skip to main content
Use whatsapp.echo_message.updated to handle this event at your webhook endpoint.

Triggers

Occurs when an outbound echo status is received for a Public REST API Agent; late lower-ranked statuses can also be delivered. Subscribe to whatsapp.echo_message.updated when you configure your webhook endpoint. This event is limited to Agents onboarded through the Public REST API. Updated echoes omit message content and type. Late lower-ranked statuses can arrive after read; record them without downgrading your stored message status.

Syntax

YCloud sends an HTTP POST request to your configured webhook URL. The following shape shows one payload variant. Angle-bracket values are placeholders; their types are listed under Parameters. Optional fields and other variants are described below.

Parameters

Validate the YCloud-Signature HTTP header before you process the JSON body. See signature validation.

Event envelope

Event payload

The four common envelope fields are required. Payload fields depend on the event variant. In each object table, Required applies when its parent object is present. Optional fields can be omitted; a sample does not make a field required.

whatsappMessage

Example

The following JSON is the body delivered to your receiver. IDs, phone numbers, and other account values are illustrative.
Correlate with the created event by id or wamid. Updated events omit message content and type.
Correlate with the created event by id or wamid. Updated events omit message content and type.
A lower-ranked source status can arrive after read. Record the event without downgrading your current message status.
This is a separate failed message, not a transition from read. Failed updates include source error details when available.
After verifying the signature and durably accepting the event, return a 2xx response. Process slow work asynchronously.
For scenario walkthroughs, see annotated examples.