List reaction events for a WhatsApp message
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.
Request
- Base URL: https://us1.platform.bird.com
- URL: https://us1.platform.bird.com/v1/whatsapp/messages/{message_id}/reaction-events
- Auth: one of:
- HTTP bearer
- API key in cookie bird_session
Path parameters
ID of the message whose reactions to read, as returned in the id field of the message.
Query parameters
Maximum number of items to return per page.
Cursor from the next_cursor field of a previous list response. Returns items immediately after the cursor position in the current sort order.
Cursor 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.
Headers
Workspace context for the request. Required for dashboard authentication and master keys. Workspace keys and access tokens already identify their workspace; send that workspace or omit the header. A different one is rejected.
Organization context for the request. Required for dashboard authentication. An API key or access token carries its own organization, so send either that organization or no header at all; a different one is rejected.
Response
Paginated list of reaction changes for this WhatsApp message.
Example response
{
"data": [
{
"id": "war_01krdgeqcxet5s7t44vh8rt9mg",
"emoji": "👍",
"status": "received",
"from": {
"phone_number": "+15550001111",
"bsuid": "NL.xxxx",
"group_id": "wag_01krdgeqcxet5s7t44vh8rt9mg"
},
"error": {
"description": "Message could not be delivered.",
"meta_error_code": "131026"
},
"occurred_at": "2026-08-28T19:01:10Z"
}
],
"next_cursor": "eyJ2IjoxLCJzIjoiXCIyMDI2LTA1LTI1VDE0OjAzOjEwWlwiIiwiaSI6IjAxOTJmM2IxLTRjN2UtN2EyYi05ZDYxLThmM2E1YzJlN2I0MCJ9",
"refresh_cursor": "eyJ2IjoxLCJzIjoiXCIyMDI2LTA1LTI1VDE2OjQyOjAxWlwiIiwiaSI6IjAxOTJmM2IxLTllMDQtN2NkMy1iODE3LTJhNmY0ZDFjOGUwOSJ9"
}Changes
No recorded changes to this operation across all 3 revisions of this API.