Create or update inventory restrictions

Use the OTA_HotelAvailNotif endpoint to:

• Set the number of rooms available (BookingLimit) for a room type and date combination
• Close a room type on a specified date. Even if roomrates are open, the room type is not available for booking
• Set restrictions by specifying room type, rate plan, and date

Usage recommendations

1. Specify availability in advance: You should specify the availability of your connected properties at least 12 months in advance.

2. Use Delta Updates Only

   • Utilize the roomRateAvailability API to compare system states
   • Send only changes (deltas), not full system refreshes

3. Single Hotel Per Request

   • All updates in a request must belong to one hotel
   • Do not mix multiple hotels in the same request

4. Monthly Batching

   • Break down updates by month
   • Each request should cover a single month period

5. Room-Rate Grouping

   • Multiple room-rates can be grouped together in the same request
   • Must be for the same hotel and same month period

Endpoint

POST https://supply-xml.booking.com/hotels/ota/OTA_HotelAvailNotif

Request

Headers

Request body

Request example

The request below specifies the following:

• Sets the rooms to sell for room 36745603 to 25 from the 5th of November to and including the 17th of November 2023
• Sets the minimum stay through for room 36745603 and rate 1278606 to 2 nights from the 5th of November to and including the 17th of November 2023
• Sets the maximum stay through for room 36745603 and rate 1278606 to 5 nights from the 5th of November to and including the 17th of November 2023
• Opens the room and rate combination for booking

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelAvailNotifRQ>
  <AvailStatusMessages>
    <AvailStatusMessage BookingLimit="25" LocatorID="1">
      <StatusApplicationControl Start="2023-11-05" End="2023-11-17" InvTypeCode="36745603" />
    </AvailStatusMessage>
    <AvailStatusMessage LocatorID="2">
      <StatusApplicationControl Start="2023-11-05" End="2023-11-17" InvTypeCode="36745603" RatePlanCode="1278606" />
      <LengthsOfStay>
        <LengthOfStay Time="2" MinMaxMessageType="SetMinLOS" />
        <LengthOfStay Time="5" MinMaxMessageType="SetMaxLOS" />
      </LengthsOfStay>
      <RestrictionStatus Status="Open" />
    </AvailStatusMessage>
  </AvailStatusMessages>
</OTA_HotelAvailNotifRQ>

Response

Response body

Response examples

This section contains examples of successful and unsuccessful responses. For a detailed description of all possible errors and warnings, see Troubleshooting availability error responses.

Success response

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05"
                       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                       xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05/OTA_HotelAvailNotifRS.xsd"
                       Version="1.004" TimeStamp="2026-02-12T15:35:01.665872Z">
  <Success />
</OTA_HotelAvailNotifRS>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Success response with warnings (HTTP 200)

Warnings can be combined with success messages if the request was still processed.

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" 
                       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
                       xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05/OTA_HotelAvailNotifRS.xsd" 
                       Version="1.004" TimeStamp="2026-02-12T15:35:01.665872Z">
  <Success />
  <Warnings>
    <Warning Code="367" ShortText="Rooms to Sell were set below the Minimum Contracted rooms for these dates: 2023-11-15, 2023-11-07, 2023-11-12, 2023-11-13, 2023-11-08, 2023-11-09, 2023-11-17, 2023-11-14, 2023-11-06, 2023-11-11, 2023-11-16, 2023-11-05, 2023-11-10. The values have been amended to the Minimum Contracted Rooms."/>
  </Warnings>
</OTA_HotelAvailNotifRS>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Error response (HTTP 400)

Errors are returned without success/warnings elements.

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05"
                       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                       xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05/OTA_HotelAvailNotifRS.xsd"
                       Version="1.004" TimeStamp="2026-02-12T15:35:01.665872Z">
    <Errors>
        <Error Code="RATE_NOT_ACTIVE_FOR_ROOM" ShortText="Rate '123' is not active for room '456'" Details="room_ids: 12345; rate_ids: 45678; dates: 2026-02-12,2026-02-12; hotel_ids: 456789;"/>
    </Errors>
</OTA_HotelAvailNotifRS>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Additional information

Setting availability for child rates

While setting up availability using rate IDs that are configured as child rates, make sure the request doesn't set values for fields that are configured to inherit from the parent rate plan.

For example, if you try to set a value for min_advance_res restrictions for a child rate while the child rate is configured to follow restrictions the API returns an error.

To resolve the error, specify a rate plan ID that is either configured as a parent rate, or a child rate that does not have the following restrictions: FollowsRestrictions.

The above constraint does not apply to the FollowsClosed restriction. While creating availability using a child rate ID, you can update the status of the room type to open or close, irrespective of the value set in FollowsClosed. However, if an availability is set using a parent rate along with open/close information, then the room type status for the associated child rate is also updated. To reiterate, there is no change to the FollowsClosed restriction behaviour.

Closing room type vs. room and rate combination

You can close availability at the:

• Room type level: Useful when removing availability for all rooms of a room type that has multiple rate combinations.
• Room type and rate combination level: Useful when removing availability for a room type satisfying a specific rate combination.

Consider the following inventory:

Closing room type and rate combination

To close the availability of the Villa so that guests don't see availability from Nov 01 - Dec 10, you must close the room type (Villa) and rate combination (Off season rate) by:

1. Setting InvTypeCode to the Villa room ID
2. Setting RatePlanCode to the Off season rate ID
3. Setting RestrictionStatus Status="Close"

Closing a room type

To close the availability of a specific room type (Villa) so that guests don't see availability for a specific period, you must close the room type by:

1. Setting InvTypeCode to the Villa room ID
2. Not including RatePlanCode in the request
3. Setting RestrictionStatus Status="Close"