booking.unacknowledged
A booking changed and your system has not acknowledged the change through the revision feed. Sent once per outstanding revision, not once per check — a booking that changes again mints a new revision and alerts again. Only sent to subscriptions that ask for it; acknowledging the revision stops it.
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": "booking.unacknowledged",
"eventId": "3f1c9a2e-8b7d-4c6a-9e0f-1a2b3c4d5e6f",
"apiVersion": "2026-04",
"timestamp": "2026-05-01T12:34:56.000Z",
"data": {
"object": {
"id": 212605,
"uid": "HMX4CMA2X9",
"channel": "airbnb",
"listingId": 5668,
"customerId": 1,
"checkinDate": "2026-06-10",
"checkoutDate": "2026-06-16",
"status": "confirmed"
},
"revisionId": "b07c2490-20fa-56c1-ac16-43cc2de2f970",
"outstandingSince": "2026-06-01T09:14:22.000Z",
"outstandingHours": 26
}
}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 →