connect.session.abandoned
A user opened a Connect session and never finished it: the link ran out, or the account was connected but its rooms were never mapped. reason says what stopped them (not_finished, credentials_rejected, provider_approval_pending, mapping_not_finished, failed) and nextStep what to tell them, so you can bring them back with a new link. Sent once per session, only for sessions opened in the last 7 days.
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": "connect.session.abandoned",
"eventId": "3f1c9a2e-8b7d-4c6a-9e0f-1a2b3c4d5e6f",
"apiVersion": "2026-04",
"timestamp": "2026-05-01T12:34:56.000Z",
"data": {
"sessionId": "cs_abc123",
"state": "user_8421",
"provider": "booking",
"status": "expired",
"reason": "provider_approval_pending",
"lastErrorCode": "awaiting_designation",
"externalAccountId": "17168363",
"nextStep": "Booking.com never confirmed the property. The host must open the Booking.com Extranet and connect FantasticStay as connectivity provider, then use a new Connect session. A property that keeps another channel manager can connect with the Booking.com login (booking-extranet-login) instead.",
"createdAt": "2026-11-10T21:56:28.000Z",
"lastActivityAt": "2026-11-10T22:01:47.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 →