Partner API V1
Recovery workflow
Polling is a first-class recovery path. Use it after downtime, a webhook outage, or a dead-letter delivery.
- Poll
GET https://www.boltlabs.app/partner-api/v1/reservation-events?status=PENDINGwith the saved cursor. - Deduplicate by
event_idand apply events in reservation-version order. - Retrieve the event snapshot and, when needed, the latest reservation details.
- Update your central inventory, then push absolute room/date availability to Bolt.
- Acknowledge only after both your inventory update and availability request succeed.
Events are not deleted
Acknowledged events remain stored for audit history. They disappear from the default pending view because their status is
ACKNOWLEDGED.Push revised inventory
curl -sS -X PUT "https://www.boltlabs.app/partner-api/v1/connections/cm_connection_123/availability" -H "Authorization: Bearer partner-access-token" -H "Idempotency-Key: availability-cm_evt_123" -H "Content-Type: application/json" -d '{"updates":[{"external_room_id":"CM_ROOM_1001","date":"2026-08-20","available":2}]}'Bolt continues to reserve and release its local booking inventory immediately. When a partner sends a new absolute baseline, Bolt subtracts active Bolt reservations whose event inventory is not covered by that complete accepted room/date update. Once a complete update covers an event snapshot, Bolt records the reconciliation marker and does not subtract that reservation again. Partial or unrelated updates retain the conservative subtraction safety rule.