Skip to main content
Message events only arrive for the WhatsApp numbers selected on the webhook. Messages in both directions share these fields:

message.new

A customer sent you a message.
Media: for images, videos, voice notes and documents, image.id (or video.id, audio.id, document.id) is WhatsApp’s media id. Get a download link with Get Media URL. Links expire, so download the file soon. Button taps and list choices: a tap on a template button comes as type: "button" with button.text and button.payload. A reply button or list choice comes as type: "interactive", with interactive.button_reply or interactive.list_reply. The preview reads [Tapped button: Yes] or [Chose: Pricing].

message.sent

AdsEra sent a message to a customer: the AI agent’s reply, your team’s reply from the inbox or the WhatsApp Business app, a template, a campaign, a sequence step or a follow-up. You get one event per message, including each message of a campaign. This is a separate event from message.new on purpose: a system that answers message.new will never answer its own messages.
A template message looks like this. The preview has the values filled in, exactly as the customer saw it:
status is usually sent or pending here. Delivery and read updates follow as message.status_updated.

message.status_updated

A message you sent changed status. Use it for ticks in your CRM, and to spot failed messages.
Statuses can arrive out of order. Keep the “highest” one (read > delivered > sent), and treat failed as final for that message.

message.reaction_updated

A customer reacted to a message with an emoji, or removed their reaction.
data is the message that got the reaction, and reactionEmoji is the emoji. An empty reactionEmoji means the reaction was removed.

How previews look