Partner API V1
Partner webhooks
Bolt sends one partner-level webhook notification for each eligible reservation event. The webhook is deliberately lightweight; retrieve the event for inventory details.
Notification
POST https://your-channel-manager.example/webhooks/bolt
Content-Type: application/json
X-Bolt-Webhook-Id: cm_evt_123
X-Bolt-Webhook-Timestamp: 1785924300
X-Bolt-Webhook-Signature: sha256=<hex-digest>
X-Bolt-Request-Id: req_123
{"event_id":"cm_evt_123","event_type":"reservation.created","created_at":"2026-08-05T10:30:00.000Z","connection_id":"cm_connection_123","bolt_property_id":"789","reservation_id":"reservation_456","reservation_version":1}Verify the raw body
Sign and verify
<timestamp>.<raw-request-body> with HMAC-SHA256 and the partner secret. Do not parse and re-serialize JSON before verification. Reject timestamps outside a five-minute replay window and deduplicate on event_id.Signature verification
import { createHmac, timingSafeEqual } from "node:crypto";
export function verifyBoltWebhook(input: {
rawBody: string;
timestamp: string;
signature: string;
secret: string;
}) {
const age = Math.abs(Date.now() / 1000 - Number(input.timestamp));
if (!Number.isFinite(age) || age > 300) return false;
const expected = createHmac("sha256", input.secret)
.update(input.timestamp + "." + input.rawBody)
.digest("hex");
const received = input.signature.replace(/^sha256=/, "");
const expectedBuffer = Buffer.from(expected, "hex");
const receivedBuffer = Buffer.from(received, "hex");
return receivedBuffer.length === expectedBuffer.length &&
timingSafeEqual(expectedBuffer, receivedBuffer);
}- Any
2xxresponse marks delivery successful but does not acknowledge processing. - Network errors, timeouts, 408, 429, and 5xx responses retry immediately, then after 1 minute, 5 minutes, 15 minutes, 1 hour, 6 hours, and 24 hours.
- Ordinary 4xx responses are recorded without automatic retry. Exhausted retryable failures become
DEAD_LETTERbut stay available through pending-event polling. - Partners should return quickly and do processing asynchronously so one slow partner cannot block other integrations.
Bolt staff configure one HTTPS URL and secret per channel-manager partner. Existing partners without a webhook still receive durable reservation events through the recovery API; delivery is recorded as skipped until a webhook is configured.
Availability remains the existing absolute endpoint:PUT https://www.boltlabs.app/partner-api/v1/connections/{connectionId}/availability.
V2 reservation payloads
V2 keeps these signature headers and retry rules, and adds a full
data resource for booking_new, booking_modification, and booking_cancellation. See the V2 reservations guide.V2 base URL: https://www.boltlabs.app/partner-api/v2.