Partner API V1
Room mapping
A mapping connects one Bolt inventory group to the stable room identifier used by your channel manager. Availability requests use the external room ID, so every synchronized room must be mapped first.
Mapping relationship
Bolt room ID ↔ channel-manager external room IDGET
/connections/{connectionId}/room-mappingsReturns the current mappings for an ACTIVE connection owned by the authenticated partner.
Request
curl --request GET \
--url "$BASE_URL/connections/<CONNECTION_ID>/room-mappings" \
--header "Authorization: Bearer <ACCESS_TOKEN>"200 response
{
"request_id": "req_example",
"mappings": [
{
"bolt_room_id": "<BOLT_ROOM_ID>",
"external_room_id": "<EXTERNAL_ROOM_ID>",
"room_name": "Deluxe Room"
}
]
}PUT
/connections/{connectionId}/room-mappingsTransactionally upserts every supplied mapping. This is a partial update, not a full replacement.
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>"
}
]
}'200 response
{
"request_id": "req_example",
"mappings": [
{
"bolt_room_id": "<BOLT_ROOM_ID>",
"external_room_id": "<EXTERNAL_ROOM_ID>",
"room_name": "Deluxe Room"
}
]
}| Field | Type | Required | Rules |
|---|---|---|---|
mappings | array | Yes | One or more mapping objects to create or update. |
bolt_room_id | string | Yes | Must identify a Bolt room returned for this connection's property. |
external_room_id | string | Yes | Must be stable, unique within the connection, and at most 255 characters. |
room_name | string | Response only | Current Bolt room name, included to make reconciliation easier. |
- Saving a new Bolt room ID creates its mapping. Saving an already mapped Bolt room ID updates its external room ID.
- Mappings omitted from a request remain unchanged. The endpoint does not replace the complete mapping set.
- V1 does not provide a delete-mapping endpoint. If a mapping must be removed, coordinate with Bolt partner support.
- The complete request is applied transactionally. A conflicting or invalid mapping prevents that mapping batch from being committed.
| Condition | Result | Partner action |
|---|---|---|
| Two Bolt rooms resolve to the same external room ID within one connection. | HTTP 409 DUPLICATE_EXTERNAL_ROOM_ID | Choose a unique, stable external room ID for each Bolt room. |
| The Bolt room does not belong to the connected property. | HTTP 404 ROOM_NOT_FOUND | Refresh the connection's room list and use an ID from that response. |
| The connection is not ACTIVE. | HTTP 409 CONNECTION_NOT_ACTIVE | Re-read the connection and wait until it is ACTIVE. |
| The room still has an iCal URL or belongs to another active channel-manager connection. | HTTP 409 ROOM_AVAILABILITY_SOURCE_CONFLICT | Clear the room's iCal URL or disconnect its other active channel manager in Bolt before mapping it. |
| Availability refers to an external room ID with no mapping. | ROOM_MAPPING_NOT_FOUND | Save the mapping, then retry the corrected availability entry with a new key. |
Re-list rooms periodically and whenever a property reports an inventory change. Newly exposed Bolt rooms require a mapping before they can receive availability. If a mapped room is no longer returned, stop sending updates for it and reconcile with the property; Bolt rejects availability it cannot resolve to a current room.
External IDs are an API contract
Do not use a display name as the external room ID. Persist a stable, system-generated identifier so renaming a room does not break its mapping or availability history.