Partner API V2
Rate push
Push current prices to Bolt using a JSON contract shaped like Booking.com’s room, rate-plan, and date grouping. Bolt stores the latest price per mapped room, opaque rate-plan ID, date, and occupancy.
/connections/{connectionId}/ratesFull URL: https://www.boltlabs.app/partner-api/v2/connections/<CONNECTION_ID>/rates
curl --request PUT \
--url "https://www.boltlabs.app/partner-api/v2/connections/<CONNECTION_ID>/rates" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--header "Content-Type: application/json" \
--header "Idempotency-Key: rates:hotel-456:2026-09-20" \
--data '{
"values": [
{
"external_room_id": "CM_ROOM_1001",
"rate_plan_code": "CM_RATE_2001",
"date_from": "2026-09-20",
"date_to": "2026-09-25",
"rate": "12500.00",
"currency": "INR"
},
{
"external_room_id": "CM_ROOM_1001",
"rate_plan_code": "CM_RATE_2001",
"date": "2026-09-26",
"rates": [
{ "occupancy": 1, "rate": "11000.00" },
{ "occupancy": 2, "rate": "12500.00" }
],
"currency": "INR"
}
]
}'Inclusive dates and property timezone
date_from and date_to are inclusive. Date validation uses the connected property's IANA timezone, so send calendar dates rather than timestamps.| Field | Type | Required | Rules |
|---|---|---|---|
values | array | Yes | Must contain at least one rate group. |
external_room_id | string | Yes | Must match a room mapping saved on this connection. |
rate_plan_code | string | Yes | Stable partner rate-plan identifier; rate_plan_id is accepted as an alias. |
| date or date_from/date_to | YYYY-MM-DD string | Yes | Choose one individual date or one inclusive range. |
rate | decimal string | One of rate or rates | Positive amount with at most two decimal places. |
rates | array | One of rate or rates | Unique occupancy values from 1 through 50, each with a positive rate. |
currency | ISO 4217 string | No | Three-letter code; defaults to the property country currency. |
{
"request_id": "req_example",
"status": "PROCESSED",
"accepted": 8,
"rejected": 0,
"errors": [],
"updated_at": "2026-09-10T12:00:00.000Z"
}accepted counts expanded room/date/occupancy updates. Structural errors count as one rejected source item; an unmapped room counts each expanded update as rejected. Every error index points to the original zero-based valuesindex.
| Status | Meaning |
|---|---|
PROCESSED | Every expanded update was stored. |
PARTIALLY_PROCESSED | At least one update was stored and at least one was rejected. |
REJECTED | No expanded update was stored. |
- Dates may not be in the past property-local date.
- The maximum horizon is 730 days from the property-local date.
- A request may expand to at most 10,000 room/date/occupancy updates; larger requests return HTTP 413.
- Prices are absolute replacements, not deltas. A retry with the same idempotency key replays the original response.
Idempotency-Key is required and scoped to the authenticated partner and connection. Reusing a key with the same canonical JSON payload returns the original result; reusing it with a different payload returns HTTP 409 IDEMPOTENCY_KEY_REUSED.