List reaction events for a WhatsApp message
/v1/whatsapp/messages/{message_id}/reaction-eventsfor await (const event of bird.whatsapp.reaction.listEvents("wam_01krdgeqcxet5s7t44vh8rt9mg")) {
console.log(event.id, event.emoji, event.status);
}for event in client.whatsapp.reaction.list_events("wam_01krdgeqcxet5s7t44vh8rt9mg"):
print(event.id, event.emoji, event.status)for event, err := range client.Whatsapp.Reaction.ListEvents(context.Background(), "wam_01krdgeqcxet5s7t44vh8rt9mg", bird.WhatsappReactionListEventsParams{}) {
if err != nil {
log.Fatal(err)
}
fmt.Println(event.Id, event.Emoji, event.Status)
}foreach ($bird->whatsapp->reaction->listEvents('wam_01krdgeqcxet5s7t44vh8rt9mg') as $event) {
echo $event->getId(), ' ', $event->getEmoji(), ' ', $event->getStatus(), "\n";
}bird whatsapp reaction list-events <message-id>curl -X GET "https://us1.platform.bird.com/v1/whatsapp/messages/{message_id}/reaction-events" \
-H "Authorization: Bearer $TOKEN" \
--url-query "limit=25"{
"data": [
{
"id": "war_01krdgeqcxet5s7t44vh8rt9mh",
"emoji": "🎉",
"status": "rejected",
"from": {
"phone_number": "+13124495569"
},
"error": {
"code": "internal_error",
"description": "the receiving number is no longer connected",
"occurred_at": "2026-08-28T19:04:22Z"
},
"occurred_at": "2026-08-28T19:04:22Z"
},
{
"id": "war_01krdgeqcxet5s7t44vh8rt9mg",
"emoji": "👍",
"status": "received",
"from": {
"phone_number": "+14155550100",
"bsuid": "US.13491208655302741918"
},
"occurred_at": "2026-08-28T19:01:10Z"
}
],
"next_cursor": null,
"prev_cursor": null,
"refresh_cursor": "eyJ2IjoxLCJzIjoiMjAyNi0wOC0yOFQxOTowNDoyMloiLCJpIjoiMDE5ZTFiMDctNWQ5ZC03NjhiLTkzZTgtODRkYzUxOGQyNjkxIn0"
}
Returns the changes made to this message's reactions as a cursor-paginated list, newest first: each emoji placed, each one replaced by a different emoji, and each one taken back. Entries are never edited, so a contact who reacts, changes their mind and then removes it leaves three of them.
One case is missing rather than recorded. A reaction is matched to the
message it was placed on through a provider id we keep for 15 days, while
WhatsApp accepts a reaction on a message up to 30 days old, so one placed on
a message older than that cannot be matched and is recorded nowhere: not
here, and not in the message's reactions.
Use this to show who reacted and when, or to find out what became of a
reaction that never appeared: a failed or rejected entry carries the
reason on error. For what currently stands on the message, read its
reactions, which folds this log down to one entry per sender.
Pass the response's next_cursor back as starting_after to fetch the next
page.
Reaction events are kept for 30 days, counted from when the message they belong to was accepted rather than from the reaction itself. They therefore go at about the same time as the message, not 30 days after the last reaction on it.
Paramètres
message_idstringID of the message whose reactions to read, as returned in the id field of the message.
Paramètres de requête
limitintegerMaximum number of items to return per page.
starting_afterstringCursor from the next_cursor field of a previous list response. Returns items immediately after the cursor position in the current sort order.
ending_beforestringCursor from the prev_cursor or refresh_cursor field of a previous list response. Returns items immediately before the cursor position in the current sort order. prev_cursor returns the preceding page. refresh_cursor anchors at the first row of that response, which on a newest-first sort is how to fetch the items that have appeared since.
Contenu de la réponse
dataChanges to this message's reactions, newest first.
next_cursorCursor for the next page. Pass back as starting_after to advance forward. null when no next page exists.
prev_cursorCursor for the previous page. Pass back as ending_before to step backward. null when no previous page exists.
refresh_cursorRefresh anchor, the first row of this response. Pass back as ending_before to fetch what precedes it in the current sort order. On a newest-first sort those are the items that have appeared since; on any other sort they are the items that sort earlier, so refreshing such a list means re-fetching it instead. Non-null whenever data is non-empty; null only on an empty page. Distinct from prev_cursor.
Ressources associées
Poursuivez avec la documentation, les guides et les exemples sur ce sujet.