Partner API V2
Reservations and webhooks
V2 uses a booking revision resource for book, modify, and cancel events. Pull the durable revision, apply it to your channel-manager system, and acknowledge only after processing succeeds.
/booking_revisions/feedFull URL: https://www.boltlabs.app/partner-api/v2/booking_revisions/feed
| Method | Path | Purpose |
|---|---|---|
GET | /booking_revisions/feed | Poll unacknowledged booking revisions with limit and opaque cursor. |
GET | /booking_revisions/{revisionId} | Retrieve one immutable JSON:API booking_revision resource. |
POST | /booking_revisions/{revisionId}/ack | Acknowledge a revision after successful local processing. |
GET | /connections/{connectionId}/reservations/{reservationId} | Read the latest revision for one reservation. |
curl --get "https://www.boltlabs.app/partner-api/v2/booking_revisions/feed" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--data-urlencode "connection_id=<CONNECTION_ID>" \
--data-urlencode "limit=100"Treat meta.next_cursor as opaque. Pass it back unchanged until the feed is exhausted. Use include_acknowledged=true for an audit replay.
{
"data": {
"type": "booking_revision",
"id": "cm_revision_123",
"attributes": {
"unique_id": "reservation_456",
"booking_id": "reservation_456",
"property_id": "PARTNER_PROPERTY_789",
"status": "modified",
"revision_id": "cm_revision_123",
"reservation_version": 2,
"arrival_date": "2026-09-20",
"departure_date": "2026-09-22",
"amount": "25000.00",
"currency": "INR",
"payment_collect": "property",
"customer": {
"name": "Asha",
"surname": "Sharma",
"mail": "asha@example.com",
"phone": "+919999999999"
},
"rooms": [
{
"index": 0,
"room_type_code": "CM_ROOM_1001",
"rate_plan_code": "CM_RATE_2001",
"checkin_date": "2026-09-20",
"checkout_date": "2026-09-22",
"amount": "25000.00",
"days": {
"2026-09-20": "12500.00",
"2026-09-21": "12500.00"
},
"occupancy": { "adults": 2, "children": 0, "infants": 0 },
"guests": [{ "name": "Asha", "surname": "Sharma" }]
}
],
"services": [],
"notes": null
}
}
}status: newrepresents a booked reservation.status: modifiedrepresents a changed booking and contains the complete latest room and guest snapshot.status: cancelledrepresents a cancellation; room and guest details remain available for reconciliation.- Amounts and day rates are decimal strings. Do not parse them as integer minor units without applying the currency contract.
curl --request POST \
--url "https://www.boltlabs.app/partner-api/v2/booking_revisions/<REVISION_ID>/ack" \
--header "Authorization: Bearer <ACCESS_TOKEN>"Acknowledge after persistence
Bolt sends the same signed webhook envelope used by V1, with a fulldata resource for V2 events. The event names are booking_new, booking_modification, and booking_cancellation.
POST https://your-channel-manager.example/webhooks/bolt
Content-Type: application/json
X-Bolt-Webhook-Id: cm_revision_123
X-Bolt-Webhook-Timestamp: 1789041600
X-Bolt-Webhook-Signature: sha256=<hex-digest>
X-Bolt-Request-Id: req_123
{
"event": "booking_modification",
"event_type": "reservation.modified",
"event_id": "cm_revision_123",
"property_id": "PARTNER_PROPERTY_789",
"booking_id": "reservation_456",
"reservation_id": "reservation_456",
"revision_id": "cm_revision_123",
"reservation_version": 2,
"data": { "type": "booking_revision", "id": "cm_revision_123", "attributes": { "status": "modified" } }
}- Verify
timestamp + "." + rawBodywith HMAC-SHA256 before parsing JSON. - Deduplicate on
event_idorrevision_id; both identify the immutable revision. - Respond with HTTP 2xx quickly, then pull the revision if processing is asynchronous. The durable feed remains the recovery path.
V1 reservation-event endpoints remain available for inventory-only integrations. New integrations should use V2 so guest, room, amount, currency, and cancellation data travel together in one immutable revision.