Partner API V1
Getting started
Follow this sequence to move an approved property request from PENDING to an active, mapped connection and send the first calendar availability update.
Use server-side credentials only
Replace every angle-bracket placeholder with the corresponding value from Bolt or your own system.
BASE_URL="https://www.boltlabs.app/partner-api/v1"
CLIENT_ID="<CLIENT_ID>"
CLIENT_SECRET="<CLIENT_SECRET>"
ACCESS_TOKEN="<ACCESS_TOKEN>"
CONNECTION_ID="<CONNECTION_ID>"
BOLT_ROOM_ID="<BOLT_ROOM_ID>"
EXTERNAL_ROOM_ID="<EXTERNAL_ROOM_ID>"
EXTERNAL_PROPERTY_ID="<EXTERNAL_PROPERTY_ID>"Bolt manually approves partners and issues a client ID and client secret. There is no self-service registration or sandbox credential flow in V1.
/auth/tokencurl --request POST \
--url "$BASE_URL/auth/token" \
--header "Content-Type: application/json" \
--data '{
"client_id": "<CLIENT_ID>",
"client_secret": "<CLIENT_SECRET>"
}'/connections?status=PENDING&limit=100curl --request GET \
--url "$BASE_URL/connections?status=PENDING&limit=100" \
--header "Authorization: Bearer <ACCESS_TOKEN>"Match the Bolt property confidently in your own system, then accept the request with your stable external property ID.
curl --request POST \
--url "$BASE_URL/connections/<CONNECTION_ID>/accept" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--header "Content-Type: application/json" \
--data '{
"external_property_id": "<EXTERNAL_PROPERTY_ID>"
}'/connections/<CONNECTION_ID>/roomscurl --request GET \
--url "$BASE_URL/connections/<CONNECTION_ID>/rooms" \
--header "Authorization: Bearer <ACCESS_TOKEN>"Map each Bolt room ID to the external room ID used by your channel manager. The endpoint upserts supplied mappings and retains mappings omitted from the request.
curl --request PUT \
--url "$BASE_URL/connections/<CONNECTION_ID>/room-mappings" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--header "Content-Type: application/json" \
--data '{
"mappings": [
{
"bolt_room_id": "<BOLT_ROOM_ID>",
"external_room_id": "<EXTERNAL_ROOM_ID>"
}
]
}'Use a unique Idempotency-Key for each logical batch. This example sets one date to three available units and closes the inclusive five-date range that follows.
curl --request PUT \
--url "$BASE_URL/connections/<CONNECTION_ID>/availability" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--header "Content-Type: application/json" \
--header "Idempotency-Key: availability:<EXTERNAL_PROPERTY_ID>:batch-001" \
--data '{
"updates": [
{
"external_room_id": "<EXTERNAL_ROOM_ID>",
"date": "2026-08-20",
"available": 3
},
{
"external_room_id": "<EXTERNAL_ROOM_ID>",
"from": "2026-08-21",
"to": "2026-08-25",
"available": 0
}
]
}'Availability 0 means unavailable
available: 0 closes that mapped room for the supplied date. It is not a stop-sell field or a separate restriction.Read the connection after a successful batch and confirm thatlast_availability_sync_at changed. Bolt updates it when at least one expanded room-date entry succeeds.
curl --request GET \
--url "$BASE_URL/connections/<CONNECTION_ID>" \
--header "Authorization: Bearer <ACCESS_TOKEN>"- If a request times out, retry the same canonical JSON payload with the same idempotency key.
- A completed duplicate replays the stored response without applying the update again.
- Reusing a key with a different payload returns HTTP 409. A key whose first request is still in flight also returns HTTP 409.
- Inspect item-level errors in partial-success responses and submit a new batch only for corrected or failed entries.
- Respect HTTP 429 and retry with backoff rather than increasing concurrency.