Partner API V1

Bolt Channel Manager Partner API

A server-to-server API for approved channel managers to discover property connection requests, synchronize reservation inventory notifications, and push absolute calendar availability into Bolt.

Production base URL

https://www.boltlabs.app/partner-api/v1

Shell
BASE_URL="https://www.boltlabs.app/partner-api/v1"

Approval is required

Bolt provisions partner credentials manually. Properties do not create or share API secrets, property tokens, or connection keys with a channel manager.

V2 scope

V2 adds prices and complete reservation payloads while keeping the V1 inventory endpoints available.

Rate push

Send inclusive room, rate-plan, and date groups with either one base rate or occupancy-specific rates.

https://www.boltlabs.app/partner-api/v2/connections/:connectionId/rates

Reservations and webhooks

Pull booking revisions in a JSON:API resource and receive signed book, modification, and cancellation notifications.

Book · modify · cancel

V1 scope

V1 has one purpose: keeping Bolt calendar inventory aligned with an approved channel manager.

Supported

  • Partner authentication with a client ID and secret
  • Property connection discovery and acceptance
  • Bolt room listing and external room mapping
  • Individual-date and date-range availability updates
  • Idempotent retries and partial-failure reporting
  • Versioned reservation inventory events and recovery polling
  • Signed webhook notifications with explicit acknowledgement

Not supported in V1

  • Pricing, rates, or rate plans in V1
  • Minimum-stay or arrival/departure restrictions
  • Guest, payment, card, pricing, or property-content data
  • Partner-created reservations, OAuth, or a self-service sandbox

Integration flow

  1. 1

    Bolt issues partner credentials

    Approved channel managers receive a client ID and client secret directly from Bolt.

  2. 2

    A property requests the connection

    The property selects the channel manager in Bolt, creating a PENDING connection for that partner.

  3. 3

    The partner accepts the property

    The channel manager finds the pending connection, matches the property in its own system, and supplies its external property ID.

  4. 4

    Rooms are mapped

    The partner reads Bolt room types and saves a stable mapping to its external room IDs.

  5. 5

    Availability is synchronized

    The partner sends idempotent date or date-range updates. An availability value of 0 closes the room for that date.

Reservation notifications complete the loop

Bolt sends a lightweight, signed notification when a confirmed Bolt reservation changes mapped inventory. Retrieve the immutable event, update your central inventory, push revised absolute availability, and then acknowledge the event. Availability values remain absolute, never deltas.

Start building