Partner API V1
Connections
A connection represents one Bolt property asking to integrate with one approved channel-manager partner. Partner credentials never grant access to properties that selected a different partner.
/connections| Query parameter | Required | Rules | Description |
|---|---|---|---|
status | No | PENDING, ACTIVE, REJECTED, PAUSED, or DISCONNECTED | Filters by the current connection state. |
limit | No | Integer from 1 to 100; default 100 | Maximum number of connections returned. |
cursor | No | Opaque string from the prior response | Continues listing after the previous page. |
curl --request GET \
--url "$BASE_URL/connections?status=PENDING&limit=100" \
--header "Authorization: Bearer <ACCESS_TOKEN>"{
"request_id": "req_example",
"connections": [
{
"connection_id": "<CONNECTION_ID>",
"status": "PENDING",
"property": {
"id": 123,
"name": "Mountain View Resort",
"city": "Manali",
"country": "IN",
"timezone": "Asia/Kolkata"
},
"external_property_id": null,
"requested_at": "2026-08-05T07:00:00.000Z",
"accepted_at": null,
"rejected_at": null,
"rejection_reason": null,
"last_availability_sync_at": null,
"capabilities": ["availability", "rates", "reservations"]
}
],
"next_cursor": null
}| Field | Type | Meaning |
|---|---|---|
request_id | string | Top-level correlation identifier for the API request. |
connection_id | string | Stable Bolt connection identifier used in all connection-scoped paths. |
status | string | Current lifecycle state. Treat values as case-sensitive. |
property | object | Bolt property summary. id is numeric; name, city, country, and timezone support matching. |
external_property_id | string or null | Partner property identifier supplied when the connection is accepted. |
requested_at, accepted_at, rejected_at | ISO 8601 string or null | Connection lifecycle timestamps in UTC. |
rejection_reason | string or null | Partner-supplied reason recorded when a connection is rejected. |
last_availability_sync_at | ISO 8601 string or null | Time of the most recent availability request with at least one successful room-date entry. |
capabilities | string array | Enabled V1 capability. The current value is availability. |
next_cursor | string or null | Top-level list cursor. Null means that no additional page exists. |
When next_cursor is not null, send it unchanged as the next request's cursor. Do not parse, modify, or persist assumptions about the cursor format. A null value means there are no more results for that filter.
curl --request GET \
--url "$BASE_URL/connections?status=PENDING&limit=100&cursor=<CURSOR>" \
--header "Authorization: Bearer <ACCESS_TOKEN>"/connections/{connectionId}curl --request GET \
--url "$BASE_URL/connections/<CONNECTION_ID>" \
--header "Authorization: Bearer <ACCESS_TOKEN>"{
"request_id": "req_example",
"connection": {
"connection_id": "<CONNECTION_ID>",
"status": "ACTIVE",
"property": {
"id": 123,
"name": "Mountain View Resort",
"city": "Manali",
"country": "IN",
"timezone": "Asia/Kolkata"
},
"external_property_id": "<EXTERNAL_PROPERTY_ID>",
"requested_at": "2026-08-05T07:00:00.000Z",
"accepted_at": "2026-08-05T07:05:00.000Z",
"rejected_at": null,
"rejection_reason": null,
"last_availability_sync_at": null,
"capabilities": ["availability", "rates", "reservations"]
}
}/connections/{connectionId}/acceptcurl --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>"
}'external_property_idis required and should remain stable for the life of the connection. It can contain at most 255 characters.- A successful acceptance changes the connection from PENDING to ACTIVE and records the acceptance time.
- Repeating acceptance with the same external property ID returns the active connection without creating another connection.
- Repeating acceptance with a different external property ID returns HTTP 409
CONNECTION_ALREADY_ACCEPTED.
/connections/{connectionId}/rejectcurl --request POST \
--url "$BASE_URL/connections/<CONNECTION_ID>/reject" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--header "Content-Type: application/json" \
--data '{
"reason": "PROPERTY_NOT_FOUND"
}'Only a PENDING connection can transition to REJECTED. The required reason can contain at most 255 characters and is stored with the connection. Repeating the same rejection and reason returns the current connection without creating another change.
| Status | Meaning | Permitted partner actions |
|---|---|---|
PENDING | The property requested this partner but the partner has not completed matching. | List, read, accept, or reject. |
ACTIVE | The partner accepted the matched property. | Read rooms and mappings, upsert mappings, and send availability. |
REJECTED | The partner could not accept the requested property. | List and read only. Wait for a new property-side request. |
PAUSED | Synchronization is temporarily suspended. | List and read only. Do not send availability until ACTIVE again. |
DISCONNECTED | The property ended the connection. | List and read only. Room and availability writes are rejected. |
Poll GET /connections?status=PENDING to discover new property requests and periodically reconcile ACTIVE, PAUSED, and DISCONNECTED states. Reservation changes use the separate signed webhook and pending-event recovery workflow; a disconnected connection is no longer readable for reservation data.
Do not infer access from a property ID