reservation.message.reaction
Someone on the conversation added or removed a reaction on a message. action is added or removed; reaction carries the emoji, who and when. The message's reactions on GET /v1/conversations/{id}/messages reflects it. Airbnb reports reactions; other channels do not fire this event.
Payload
Every delivery uses the same outer envelope (event, eventId, apiVersion, timestamp, data). Dedupe on eventId — it stays stable across retries and replays, while the X-Repull-Delivery-Id header changes on every attempt.
{
"event": "reservation.message.reaction",
"eventId": "3f1c9a2e-8b7d-4c6a-9e0f-1a2b3c4d5e6f",
"apiVersion": "2026-04",
"timestamp": "2026-05-01T12:34:56.000Z",
"data": {
"reservationId": 235970,
"threadId": "900301",
"externalThreadId": "2648057088",
"listingId": 23893,
"channel": "airbnb",
"messageId": "1854462",
"externalMessageId": "32877308873",
"action": "added",
"reaction": {
"id": "9e0b945a-b03d-4e28-ad48-5f7fc706a67f",
"emoji": "❤️",
"by": {
"type": "guest",
"name": "Maya"
},
"at": "2026-09-25T13:06:02.000Z"
}
}
}Verifying signatures
Every delivery includes a timestamped X-Repull-Signature header of the form t=<unix_ts>,v1=<hex>, where v1 is HMAC-SHA256(signing_secret, `${t}.${raw_body}`). Verify it before processing — see Verify Signatures for full Node.js and Python examples.
Use the raw body
Tip: Acknowledge with a 2xx status within 10 seconds. Failed deliveries are retried 7 times over 24 hours, with backoff.Webhook reliability →