Retrieve inventory and rate details

The xml/roomrateavailability endpoint returns inventory information per property from Booking.com.

The response contains the following information:

• Room, rate and date information.
• Number of booked rooms.
• Number of cancelled rooms.
• Whether a room and rate combination is closed for a certain date.
• Only available in v1.1 Whether a room type is closed. When a room type is closed, the room type will not be available for booking for the specified period, irrespective of whether the room has an open room and rate combination.
• Number of minimum contracted rooms for a room and rate combination per date.
• Number of minimum contracted rooms for a room and rate combination per date.
• Number of rooms left to sell.

HTTP Request

POST https://supply-xml.booking.com/hotels/xml/roomrateavailability

Difference between roomrateavailability endpoint v1.0 and v1.1

The roomrateavailability endpoint has two versions currently. When migrating to the v1.1 roomrateavailability endpoint, you can view whether a room type is closed.

For an update on the changes, see the migration guide.

Header parameter

Sample header

POST 'https://supply-xml.booking.com/hotels/xml/availability' \
--header 'Accept-Version: 1.1' \
--header 'Authorization: Basic THVjLVNhbXVlbMblhWTdlOCghQ29qaU9pNmxlWSpIWXU9OigvS2meQpQ12puj' \
--header 'Content-Type: application/xml'

Request body parameters

Request body example

<request>
  <hotel_id>367456</hotel_id>
  <version>1.0</version>
  <number_of_days>2</number_of_days>
  <start_date>2023-09-19</start_date>
  <room_level>1</room_level>
  <room_id>12302</room_id>
</request>

Response body example (room_level = 1)

<result>
  <room room_id="26551401">
    <date
      min_contracted_rooms="0"
      min_contracted_rooms_until="0"
      rooms_to_sell="0"
      value="2017-09-01"  
      closed="0">
      <rate
        booked="0"
        cancelled="0"
        closed="1"
        closed_on_arrival="0"
        closed_on_depart="0"
        exact_stay_arrival="0"
        length_of_stay="0"
        max_advance_res=""
        max_stay_arrival="0"
        max_stay_through="0"
        min_advance_res=""
        min_contracted_rooms="0"
        min_contracted_rooms_until="0"
        min_stay_arrival="0"
        min_stay_through="0"
        occupancy="2"
        policygroup=""
        price="35.00"
        price_single="35.00"
        rate_id="910013"/>
    </date>
  </room>
  <warnings>
        <warning>We excluded the following rooms from the result, because they have no room-level availability and the request contained room_level=1. room_ids: 12301, 12303</warning>
  </warnings>
</result>

Notes:

• Booking.com generally handles availability at room level. If you request availability information at rate level for a property with a room level inventory, the response is likely to be inaccurate.
• If you specify room_level=1, then the API ignores rooms that have no room-level availability. See the warning in the sample above.
• If you specify room_level=0, then the API ignores room-level closure information.

Response body example (room_level = 0)

<result>
    <roomrate
      booked="0"
      cancelled="0"
      closed="0"
      date="2023-09-19"
      rate_id="12345678"
      room_id="12302"
      rooms_to_sell="2"/>
    <!-- More <roomrate> elements would follow here. Skipped for brevity. -->
</result>
<!-- RUID: [UmFuZG9tSVYkc2RlIyetc] -->

Response body elements

The following attributes are applicable for both roomrate and rate elements.

HTTP error list

If the request returns an error, the xml/roomrateavailability endpoint returns an error description with the fault code=400. The following table captures all the error validations and their possible resolutions.

Warning