channel.sync.failed
A push of availability, rates or content to a connected channel did not land. total says whether NO mapping accepted it or only some — a partial push is the more dangerous case, because the listing is live somewhere and inconsistent. Each entry in failures names the channel and why, and kind: "unknown" means we could not classify it, never that the channel refused. When reservationId is set the push was blocking dates for a booking just taken: those nights are sold on one channel and still open on another.
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": "channel.sync.failed",
"eventId": "3f1c9a2e-8b7d-4c6a-9e0f-1a2b3c4d5e6f",
"apiVersion": "2026-04",
"timestamp": "2026-05-01T12:34:56.000Z",
"data": {
"type": "channel.sync.failed",
"test": true
}
}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 →