Partner API V1
Rooms
Fetch the Bolt room types belonging to an ACTIVE property connection before saving external room mappings. V1 exposes inventory groups, not individual physical room numbers.
GET
/connections/{connectionId}/roomsThe connection must belong to the authenticated partner and be ACTIVE.
Request
curl --request GET \
--url "$BASE_URL/connections/<CONNECTION_ID>/rooms" \
--header "Authorization: Bearer <ACCESS_TOKEN>"200 response
{
"request_id": "req_example",
"property": {
"id": 123,
"name": "Mountain View Resort",
"timezone": "Asia/Kolkata"
},
"rooms": [
{
"id": "<BOLT_ROOM_ID>",
"name": "Deluxe Room",
"total_units": 8,
"max_occupancy": 3,
"mapped_external_room_id": null
}
]
}| Field | Type | Meaning |
|---|---|---|
id | string | Stable Bolt room UUID used as bolt_room_id in mapping requests. Legacy rooms can return a numeric ID encoded as a string. |
name | string | Property-facing name of the Bolt room type. |
total_units | integer | Maximum inventory configured for that Bolt room type. Availability cannot exceed it. |
max_occupancy | integer or null | Maximum guest occupancy configured for the room type. |
mapped_external_room_id | string or null | The current external room mapping for this connection, when one exists. |
One Bolt room is an inventory group
A room in this API represents a bookable Bolt room type with a shared inventory count, such as “Deluxe Room.” It does not represent physical units such as room 101 or room 102.
- Fetch rooms after accepting a connection and before each mapping reconciliation.
- A newly created Bolt room becomes available to the partner on a subsequent room-list request; it must be mapped before availability can be sent using an external room ID.
- The response is the source of truth for room types currently exposed to the connection. V1 does not expose internal room records or an editable room-status field.
- If a previously mapped room disappears from the room list, stop sending it and reconcile with the property. Availability writes for a room Bolt can no longer resolve are rejected.
Calling this endpoint for PENDING, REJECTED, PAUSED, or DISCONNECTED connections returns HTTP 409 CONNECTION_NOT_ACTIVE. Re-read the connection before retrying; do not continue room or availability writes until it is ACTIVE.
Do not expose raw room data
Persist only the identifiers and fields required for matching. The Partner API intentionally excludes pricing, booking, guest, payment, property-owner, and internal database fields.