Managing roomrates¶

A roomrate (also known as a product) is the unique combination of a room type and a rate plan with conditions. These conditions can consist of:

Policy: Refers to a combination of a cancellation and a prepayment policy.
Cancellation policy: Refers to whether there is and what the penalty is for a guest if they cancel a booking within a given time frame.
Prepayment policy: Refers to whether and when the property takes a prepayment from the guest.
Override policy: Refers to a policy that you can set on certain dates to overwrite the policy already assigned to a roomrate.
Booking restrictions: Refers to certain restrictions you can set when it comes to booking a roomrate.
Meal plan: Refers to whether there is and what the meal plan is assigned to the roomrate.

You need roomrates to create and push inventory (availability) and rates (prices).

Managing policies and restrictions¶

It is very important to properly understand what policies and restrictions are and how to assign them to roomrates in the context of the /ota/OTA_HotelProductNotif endpoint. Read this before you start creating roomrates.

What is a policy?¶

You must see a policy as a combination of a cancellation policy and a prepayment policy.

To find all the available cancellation codes, see cancellation policies. You can find free and non-free cancellations. Each one specifies the time frame in which a guest can cancel (with the exception of non-refundable with code 1) and what the possible penalty is for a guest if they cancel after a specific deadline or deadlines.

A policy can also include a prepayment. If prepayment is required, it further specifies whether the prepayment must happen after a guest makes a reservation (after_reservation_is_made) or when the guest can no longer cancel for free (after_cancellation_begins).

What is an override policy?¶

An override policy is just a policy. However, you use it to overwrite the main policy of a roomrate for a specified date range. Let's say a property uses a flexible policy for most of the year, but they want to use a non-refundable policy for their peak season. That would be a good use case for a policy override.

What are restrictions?¶

Restrictions enable you to specify when a roomrate with a specific policy is and is not possible to book. You can set the following restrictions:

MinAdvancedBookingOffset: Refers to point in time until a roomrate is still bookable relative to the check-in. In other words, this specifies the moment from when a guest can no longer book the roomrate. The search date is counted as one of the days in the restriction length.
MaxAdvancedBookingOffset: Refers to point in time from when a roomrate becomes bookable relative to the check-in. In other words, this specifies the moment from when a guest can start booking the roomrate. The search date is counted as one of the days in the restriction length.

You can also set the specific hours in which a roomrate is available per day, but this is not recommended.

Mapping room types and rate plans¶

To map your room types and rate plans to Booking.com's, you should use the retrieving roomrates endpoint. You could also use the retrieving room types and retrieving rate plans endpoints, but these contain less complete information. You could still use either to troubleshoot issues with mapping as needed.

Creating a roomrate¶

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

The POST /ota/OTA_HotelProductNotif request enables you to create roomrates for your property.

Creating or updating¶

To create a roomrate you set ProductNotifType to New. If you want to update a roomrate, you set ProductNotifType to Overlay.

Elements for creating a roomrate¶

To create a roomrate on Booking.com, the following basic elements are required:

Property id
Room type id
Rate plan id

To further expand a roomrate, it is recommended to also add:

Value add inclusions: To indicate whether there is a meal plan and if so what that meal plan is.
Policy: To assign an existing policy (combination of cancellation and prepayment) to a roomrate.

The following elements are optional:

Override policy
Booking rules

Assigning policies to roomrates¶

You can only assign existing policies using the /ota/OTA_HotelProductNotif endpoint. This means that if you want to create or update policies for a property, you must either:

Use the HotelDescriptiveContentNotif endpoint if you have implemented it.
Tell the property to use their property page on the Booking.com extranet to create a policy there.

How do you assign a policy?¶

To assign a policy to a roomrate, follow these steps:

Retrieve the property's existing policies either by:
- Retrieving the property details: You need the HotelDescriptiveInfo endpoint to retrieve all the existing policies on the property level.
- Retrieving the policies that are already assigned to existing roomrates.
You only need the cancellation policy code, because the prepayment policy is implicitly connected to this cancellation policy code. To know what each code represents, see the cancellation policies.
Assign the policy by adding the code to the PolicyCode element (CancelPolicy > CancelPenalty > PolicyCode).

How do you assign an override policy?¶

To assign an override policy to a roomrate, follow these steps:

Retrieve the property's existing policies either by:

Retrieving the property details: You need the HotelDescriptiveInfo endpoint to retrieve all the existing policies on the property level.
Retrieving the policies that are already assigned to existing roomrates.

For policy overrides, you need the policy name and not the policy code. If you use the HotelDescriptiveInfo endpoint, you can use the name under PolicyName (CancelPolicy > CancelPenalty > PolicyName). If you only retrieve policies that are already assigned to existing roomrates., you must look at the name under policy (room > rates > rate > policy) and find its policy override name equivalent in the following table:

`roomrate` name	policy override name
General	PTT_GENERAL
Non-refundable	PTT_NON_REFUNDABLE
Special conditions	PTT_SPECIAL_CONDITIONS
Special conditions 2	PTT_SPECIAL_CONDITIONS_2
Special conditions 3	PTT_SPECIAL_CONDITIONS_3
Special conditions 4	PTT_SPECIAL_CONDITIONS_4
Fully flexible	PTT_FULLY_FlEXIBLE

Assign the policy by adding the policy override name to the PolicyName element (OverridePolicies > OverridePolicy > PolicyName).

→ To know what each policy name represents, find the policy code and see the cancellation policies.

Body parameters¶

The following table describes what elements you must add in the request body:

Element	Attribute	Description	Type	Required/Optional	Notes
`OTA_HotelProductNotifRQ`		Contains the `HotelProducts` array.	object	required
> `HotelProducts`		Contains the `HotelProduct` objects.	array	required
	`HotelCode`	Specifies the unique ID of the property you create roomrates for.	integer	required
>> `HotelProduct`		Contains the roomrate information.	object	required
	`ProductNotifType`	Specifies whether the request is to create a roomrate (`New`) or modify an existing one (`Overlay`).	enum	required	Possible values are `New` and `Overlay`. You must use `New` to create a roomrate.
>>> `RoomTypes`		Contains a `RoomType` object.	object	required
>>>> `RoomType`		Contains the room type information.	object	required
	`RoomTypeCode`	Specifies the room type id.	integer	required
	`MaxOccupancy`	Specifies the maximum occupancy of the roomtype.	integer	required	Note that specifying this value overrides the value set at the time of creating or updating the roomtype. Also, the pricing type of the roomrate is changed to RLO.
>>> `RatePlans`		Contains a `RatePlan` object.	object	required
>>>> `RatePlan`		Contains the rate plan information.	object	required
	`RatePlanCode`	Specifies the rate plan id.	integer	required
>>> `ValueAddInclusions`		Contains a `MealPlan` object.	object	optional
>>>> `MealPlan`		Contains the meal plan information.	object	optional	If you do not include this element, the default is no meal plan included.
	`MealPlanCode`	Specifies the meal plan id.	integer	optional	To see the list of meal plan codes at Booking.com, see meal plan codes.
>>> `PolicyInfo`		Contains the cancellation and booking policy objects.	object	optional
>>>> `CancelPolicy`		Contains the `CancelPenalty` objects.	object	optional
>>>>> `CancelPenalty`		Contains the policy information.	object	optional
	`PolicyCode`	Specifies the policy (cancellation and prepayment policy combination) you assign to the roomrate.	integer	optional	To see the list of cancellation and prepaymeny policy codes at Booking.com, see cancellation and prepayment polices.
>>>> `OverridePolicies`		Contains the `OverridePolicy` objects.	object	optional
>>>>> `OverridePolicy`		Contains the override policy information, which overwrites other policies set for this roomrate on the dates specified within the object.	object	optional
	`PolicyName`	Specifies the name of the override policy.	string	optional
>>>>>> `BookDates`		Contains the `BookDate` objects.	object	optional
>>>>>>> `BookDate`		Contains the book date information, which specify the dates when the override policy overwrites other policies.	object	optional
	`Start`	Specifies the start date of the override policy.	string	optional	Follows the format: `YYYY-MM-DD`.
	`End`	Specifies the end date of the override policy.	string	optional	Follows the format: `YYYY-MM-DD`.
>>>>>> `ActiveWeekdays`		Contains the `ActiveWeekDay` objects.	object	optional
>>>>>>> `ActiveWeekday`		Contains the active week day information, which specify the days when the override policy overwrites other policies.	object	optional
	`Day`	Specifies the name of the day of the week.	string	optional	Possible values are: `Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, `Saturday`, and `Sunday`.
>>>> `BookingRules`		Contains the `BookingRule` objects.	object	optional
>>>>> `BookingRule`		Contains the booking policy information.	object	optional
	`MinimumAdvancedBookingOffset`	Specifies the minimum amount of time in which a room type must be booked relative to midnight (24:00 CE(S)T) of the check-in date start.	string	optional	This is the format used: `P[0-9]+(Y,M,D,H)`. An example is: P5H means the room must be booked before 19:00 on the day before the check-in date.
	`MaximumAdvancedBookingOffset`	Specifies the maximum amount of time in which a room type can be booked relative to midnight (24:00 CE(S)T) of the check-in date start.	string	optional	This is the format used: `P[0-9]+(Y,M,D,H)`. An example is: P14D means the room can be booked a maximum of 14 days before the check-in date.
	`ReleaseTimeOfDayStart`	Specifies the time of the day the room type can start being booked.	HH:MM	optional	This allows time intervals of 15 minutes starting at midnight. For example: 10:15.
	`ReleaseTimeOfDayEnd`	Specifies the time of the day the room type can no longer be booked.	HH:MM	optional	This allows time intervals of 15 minutes starting at midnight. For example: 18:00.

Request body example¶

The following is a request body example:

<OTA_HotelProductNotifRQ>
  <HotelProducts HotelCode="64231">
    <HotelProduct ProductNotifType="New">
      <RoomTypes>
        <RoomType RoomTypeCode="6423112" />
      </RoomTypes>
      <RatePlans>
        <RatePlan RatePlanCode="12483478" />
      </RatePlans>
      <ValueAddInclusions>
        <MealPlan MealPlanCode="19" />
      </ValueAddInclusions>
      <PolicyInfo>
        <BookingRules>
          <BookingRule MinAdvancedBookingOffset="P1D" />
          <BookingRule MaxAdvancedBookingOffset="P14D" />
        </BookingRules>
        <CancelPolicy>
          <CancelPenalty PolicyCode="15"/>
        </CancelPolicy>
        <OverridePolicies>
          <OverridePolicy PolicyName="PTT_NON_REFUNDABLE">
            <BookDates>
              <BookDate Start="2021-06-06" End="2021-06-29"/>
              <BookDate Start="2021-07-06" End="2021-07-29"/>
            </BookDates>
            <ActiveWeekdays>
              <ActiveWeekday Day="Friday"/>
              <ActiveWeekday Day="Saturday"/>
              <ActiveWeekday Day="Sunday"/>
            </ActiveWeekdays>
          </OverridePolicy>
        </OverridePolicies>
      </PolicyInfo>
    </HotelProduct>
  </HotelProducts>
</OTA_HotelProductNotifRQ>

Response body example¶

The following is a successful response body example:

<OTA_HotelProductNotifRS>
  <Success />
</OTA_HotelProductNotifRS>
<!-- RUID: [UmFuZG9tSVYkc2RlIyh9YUedwgregreg3/GEVjlG+mTXmB9OkyhGlAKEMxDhfrI] -->

Response body parameters¶

The following table describes the response elements:

Element	Description	Type	Notes
`OTA_HotelProductNotifRS`	Contains the response data.	object
> `success`	Indicates the success of the request.	object
`ruid`	Specifies the unique ID of the request.	string	You can send this ID to Booking.com customer support if you run into an issue. This can help to understand what went wrong.

Updating a roomrate¶

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

The POST /ota/OTA_HotelProductNotif request enables you to update roomrates for your property.

When updating a roomrate, it is very important to do the following:

Set InvNotifType to Overlay.
Include all existing information: This means you send the roomrate information as if you create a new roomrate, changing the elements you want to update.
→ To retrieve most of your roomrate information, see retrieving roomrates.

→ To retrieve the policy names in the same way as you created them, see the CancelPolicy elements when retrieving property details.

Requirements for updating a roomrate¶

To create a roomrate on Booking.com, the following basic elements are required:

Property id
Room type id
Rate plan id

Body parameters¶

The following table describes what elements you must add in the request body:

Element	Attribute	Description	Type	Required/Optional	Notes
`OTA_HotelProductNotifRQ`		Contains the `HotelProducts` array.	object	required
> `HotelProducts`		Contains the `HotelProduct` objects.	array	required
	`HotelCode`	Specifies the unique ID of the property you create roomrates for.	integer	required
>> `HotelProduct`		Contains the roomrate information.	object	required
	`ProductNotifType`	Specifies whether the request is to create a roomrate (`New`) or modify an existing one (`Overlay`).	enum	required	Possible values are `New` and `Overlay`. You must use `New` to create a roomrate.
>>> `RoomTypes`		Contains a `RoomType` object.	object	required
>>>> `RoomType`		Contains the room type information.	object	required
	`RoomTypeCode`	Specifies the room type id.	integer	required
	`MaxOccupancy`	Specifies the maximum occupancy of the roomtype.	integer	required	Note that specifying this value overrides the value set at the time of creating or updating the roomtype. Also, the pricing type of the roomrate is changed to RLO.
>>> `RatePlans`		Contains a `RatePlan` object.	object	required
>>>> `RatePlan`		Contains the rate plan information.	object	required
	`RatePlanCode`	Specifies the rate plan id.	integer	required
>>> `ValueAddInclusions`		Contains a `MealPlan` object.	object	optional
>>>> `MealPlan`		Contains the meal plan information.	object	optional	If you do not include this element, the default is no meal plan included.
	`MealPlanCode`	Specifies the meal plan id.	integer	optional	To see the list of meal plan codes at Booking.com, see meal plan codes.
>>> `PolicyInfo`		Contains the cancellation and booking policy objects.	object	optional
>>>> `CancelPolicy`		Contains the `CancelPenalty` objects.	object	optional
>>>>> `CancelPenalty`		Contains the policy information.	object	optional
	`PolicyCode`	Specifies the policy (cancellation and prepayment policy combination) you assign to the roomrate.	integer	optional	To see the list of cancellation and prepaymeny policy codes at Booking.com, see cancellation and prepayment polices.
>>>> `OverridePolicies`		Contains the `OverridePolicy` objects.	object	optional
>>>>> `OverridePolicy`		Contains the override policy information, which overwrites other policies set for this roomrate on the dates specified within the object.	object	optional
	`PolicyName`	Specifies the name of the override policy.	string	optional
>>>>>> `BookDates`		Contains the `BookDate` objects.	object	optional
>>>>>>> `BookDate`		Contains the book date information, which specify the dates when the override policy overwrites other policies.	object	optional
	`Start`	Specifies the start date of the override policy.	string	optional	Follows the format: `YYYY-MM-DD`.
	`End`	Specifies the end date of the override policy.	string	optional	Follows the format: `YYYY-MM-DD`.
>>>>>> `ActiveWeekdays`		Contains the `ActiveWeekDay` objects.	object	optional
>>>>>>> `ActiveWeekday`		Contains the active week day information, which specify the days when the override policy overwrites other policies.	object	optional
	`Day`	Specifies the name of the day of the week.	string	optional	Possible values are: `Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, `Saturday`, and `Sunday`.
>>>> `BookingRules`		Contains the `BookingRule` objects.	object	optional
>>>>> `BookingRule`		Contains the booking policy information.	object	optional
	`MinimumAdvancedBookingOffset`	Specifies the minimum amount of time in which a room type must be booked relative to midnight (24:00 CE(S)T) of the check-in date start.	string	optional	This is the format used: `P[0-9]+(Y,M,D,H)`. An example is: P5H means the room must be booked before 19:00 on the day before the check-in date.
	`MaximumAdvancedBookingOffset`	Specifies the maximum amount of time in which a room type can be booked relative to midnight (24:00 CE(S)T) of the check-in date start.	string	optional	This is the format used: `P[0-9]+(Y,M,D,H)`. An example is: P14D means the room can be booked a maximum of 14 days before the check-in date.
	`ReleaseTimeOfDayStart`	Specifies the time of the day the room type can start being booked.	HH:MM	optional	This allows time intervals of 15 minutes starting at midnight. For example: 10:15.
	`ReleaseTimeOfDayEnd`	Specifies the time of the day the room type can no longer be booked.	HH:MM	optional	This allows time intervals of 15 minutes starting at midnight. For example: 18:00.

Request body example¶

The following is a request body example:

<OTA_HotelProductNotifRQ>
  <HotelProducts HotelCode="64231">
    <HotelProduct ProductNotifType="Overlay">
      <RoomTypes>
        <RoomType RoomTypeCode="6423112" />
      </RoomTypes>
      <RatePlans>
        <RatePlan RatePlanCode="12483478" />
      </RatePlans>
      <ValueAddInclusions>
        <MealPlan MealPlanCode="0" />
      </ValueAddInclusions>
      <PolicyInfo>
        <BookingRules>
          <BookingRule MinAdvancedBookingOffset="P1D" />
          <BookingRule MaxAdvancedBookingOffset="P14D" />
        </BookingRules>
        <CancelPolicy>
          <CancelPenalty PolicyCode="15" />
        </CancelPolicy>
        <OverridePolicies>
          <OverridePolicy PolicyName="PTT_NON_REFUNDABLE">
            <BookDates>
              <BookDate Start="2021-06-06" End="2021-06-29"/>
              <BookDate Start="2021-07-06" End="2021-07-29"/>
            </BookDates>
            <ActiveWeekdays>
              <ActiveWeekday Day="Friday"/>
              <ActiveWeekday Day="Saturday"/>
            </ActiveWeekdays>
          </OverridePolicy>
        </OverridePolicies>
      </PolicyInfo>
    </HotelProduct>
  </HotelProducts>
</OTA_HotelProductNotifRQ>

Response body example¶

The following is a successful response body example:

<OTA_HotelProductNotifRS>
  <Success />
</OTA_HotelProductNotifRS>
<!-- RUID: [UmFuZG9tSVYkc2RlIyh9YUedwgregreg3/GEVjlG+mTXmB9Owf2f+Kq=Mzyiykpi6Yx5oKzRKEMxDhfrI] -->

Response body parameters¶

The following table describes the response elements:

Element	Description	Type	Notes
`OTA_HotelProductNotifRS`	Contains the response data.	object
> `success`	Indicates the success of the request.	object
`ruid`	Specifies the unique ID of the request.	string	You can send this ID to Booking.com customer support if you run into an issue. This can help to understand what went wrong.

Removing roomrates¶

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

The POST /ota/OTA_HotelProductNotif request enables you to remove a roomrate by disconnecting the room type and rate plan.

Requirements for removing a roomrate¶

To remove a roomrate from Booking.com, you only need the following elements:

Property id
Room type id
Rate plan id

You must also set ProductNotifType to Remove.

Body parameters¶

The following table describes what elements you must add in the request body:

Element	Attribute	Description	Type	Required/Optional	Notes
`OTA_HotelProductNotifRQ`		Contains the `HotelProducts` array.	object	required
> `HotelProducts`		Contains the `HotelProduct` objects.	array	required
	`HotelCode`	Specifies the unique ID of the property you create roomrates for.	integer	required
>> `HotelProduct`		Contains the roomrate information.	object	required
	`ProductNotifType`	Specifies whether the request is to remove a roomrate.	enum	required	Value to remove a roomrate is `remove`.
>>> `RoomTypes`		Contains a `RoomType` object.	object	required
>>>> `RoomType`		Contains the room type information.	object	required
	`RatePlanCode`	Specifies the rate plan id.	integer	required
>>> `RatePlans`		Contains a `RatePlan` object.	object	required
>>>> `RatePlan`		Contains the rate plan information.	object	required

Request body example¶

The following is a request body example:

<OTA_HotelProductNotifRQ>
  <HotelProducts HotelCode="64231">
    <HotelProduct ProductNotifType="Remove">
      <RoomTypes>
        <RoomType RoomTypeCode="6423112" />
      </RoomTypes>
      <RatePlans>
        <RatePlan RatePlanCode="12483478" />
      </RatePlans>
    </HotelProduct>
  </HotelProducts>
</OTA_HotelProductNotifRQ>

Response body example¶

The following is a successful response body example:

<OTA_HotelProductNotifRS>
  <Success />
</OTA_HotelProductNotifRS>
<!-- RUID: [UmFuZG9tSVYkc2RlIyh9YUedwgregreg3/GcBkCkoW0/uhiPmwiL6pcbMzyiykpi6Yx5oKzRKEMxDhfrI] -->

Response body parameters¶

The following table describes the response elements:

Element	Description	Type	Notes
`OTA_HotelProductNotifRS`	Contains the response data.	object
> `success`	Indicates the success of the request.	object
`ruid`	Specifies the unique ID of the request.	string	You can send this ID to Booking.com customer support if you run into an issue. This can help to understand what went wrong.

Retrieving active roomrates¶

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

The POST /xml/roomrates request enables you to retrieve active roomrates for a property. You can retrieve the relevant room type and rate plan IDs. Remember to use Booking.com IDs while creating availability and not your internal IDs.

You can also use this endpoint to retrieve policy override information for active roomrates.

Retrieving pricing details in roomrate

Note that you must enable the feature: Include products extra info (include_extra_info_room_rates) using the Provider portal to see the pricing type information along with rate relation, policy overrides among others.

Body parameters¶

The following table describes what elements you must add in the request body:

Element	Description	Type	Required/Optional
`request`	Contains the request information.	object	required
> `hotel_id`	Specifies the unique ID of the property you want to retrieve the active rate plans for.	integer	required
> `policy_override_start`	Specifies the start of the date range for which you want to retrieve policy override information.	string	optional
> `policy_override_end`	Specifies the end of the date range for which you want to retrieve policy override information.	string	required if `policy_override_start` is specified

Request body example 1¶

The following is a request body example:

<request>
   <hotel_id>6314570</hotel_id>
</request>

Request body example 2¶

The following request body example retrieves roomrates that have policy overrides defined:

<request>
    <hotel_id>6314570</hotel_id>
    <policy_override_start_date>2022-06-26</policy_override_start_date>
    <policy_override_end_date>2022-07-25</policy_override_end_date>
</request>

Response body example¶

The following is a successful response body example:

<rooms>
    <room id="631457025" hotel_id="6314570" hotel_name="The Tech Western" max_children="0" room_name="Double Room">
        <rates>
            <rate id="20275653" fixed_occupancy="2" max_persons="4" policy="Special conditions" policy_id="278832781" rate_name="standard rate">
                <meal_plan meal_plan_code="0"/>
                <policies>
                    <booking_rules/>
                    <cancel_policy>
                        <cancel_penalty policy_code="12"/>
                        <policy_overrides>
                            <policy_override start_date="2022-06-25" end_date="2022-07-03" policy_code="12"/>
                        </policy_overrides>
                    </cancel_policy>
                    <guarantee_payment_policy>
                        <guarantee_payment policy_code="1" effective_from="after_reservation_is_made" required="1"/>
                        <policy_overrides>
                            <policy_override start_date="2022-06-26" end_date="2022-07-03" policy_code="after_reservation_is_made"/>
                        </policy_overrides>
                    </guarantee_payment_policy>
                </policies>
                <pricing type="RLO"/>
            </rate>
            <rate id="21532127" fixed_occupancy="2" max_persons="4" policy="Special conditions" policy_id="278832781" rate_name="Luca rate">
                <meal_plan meal_plan_code="0"/>
                <policies>
                    <booking_rules/>
                    <cancel_policy>
                        <cancel_penalty policy_code="12"/>
                    </cancel_policy>
                    <guarantee_payment_policy>
                        <guarantee_payment policy_code="1" effective_from="after_reservation_is_made" required="1"/>
                    </guarantee_payment_policy>
                </policies>
                <pricing type="RLO"/>
            </rate>
        </rates>
    </room>
</rooms>
        <!-- RUID: [UmFuZG9tSVYkc2RlIyh9YYZJoYkt+i+xKsmop1uLVhmRLuQaFc3IDL0E1x2+zdOWYz2pJVzXOVOEnAQEu+HQ4qzGv3MQ3SGU] -->

Response body parameters¶

The following table describes the response elements:

Element	Attribute	Description	Type	Notes
`rooms`		Contains the `room` objects.	object
> `room`		Contains the room type information.	object
	`id`	Specifies the unique Booking.com ID of the room type.	integer
	`hotel_id`	Specifies the unique ID of the property.	integer
	`hotel_name`	Specifies the name of the property.	string
	`max_children`	Specifies the maximum number of children allowed in the room type.	integer
	`room_name`	Specifies the name of the room type.	string
>> `rates`		Contains the `rate` objects.	object
>>> `rate`		Contains the rate plan information.	object
	`id`	Specifies the unique Booking.com ID of the rate plan.	integer
	`fixed_occupancy`	Only applicable for derived pricing types (RLO). Shows the maximum number of occupants specified when creating or updating a roomrate.	integer	This value can be different from the max_persons value set while creating the roomtype.
	`max_persons`	Specifies the maximum number of adults allowed in the room type.	integer
	`policy`	Specifies the name of the policy.	string
	`policy_id`	Specifies the unique ID of the policy.	integer
	`rate_name`	Specifies the name of the rate plan.	string
>>>> `meal_plan`		Contains the meal plan information.	object
	`meal_plan_code`	Specifies the meal plan ID.	integer	To see the list of meal plan codes at Booking.com, see meal plan codes.
>>>> `policies`		Contains the cancellation policy details.	object
>>>>> `booking_rules`		Contains the `BookingRule` objects.	object
>>>>>> `booking_rule`		Contains the booking policy information.	object
	`min_advanced_booking_offset`	Specifies the minimum amount of time in which a room type must be booked relative to midnight (24:00 CE(S)T) of the check-in date start.	string	This is the format used: `P[0-9]+(Y,M,D,H)`. An example is: P5H means the room must be booked before 19:00 on the day before the check-in date.
	`max_advanced_booking_offset`	Specifies the maximum amount of time in which a room type can be booked relative to midnight (24:00 CE(S)T) of the check-in date start.	string	This is the format used: `P[0-9]+(Y,M,D,H)`. An example is: P14D means the room can be booked a maximum of 14 days before the check-in date.
>>>> `cancel_policy`		Contains the `CancelPenalty` object.	object
>>>>> `cancel_penalty`		Contains the policy information.	object
	`policy_code`	Specifies the cancellation policy code.	integer	For a full list of all the available cancellation codes, see the cancellation policy codes.
>>>>>>> `policy_overrides`		Contains the policy override elements.	object
>>>>>>>> `policy_override`		Contains a policy override element.	object
	`start_date`	Specifies the start date of the override policy.	string	Follows the format: `YYYY-MM-DD`.
	`end_date`	Specifies the end date of the override policy.	string	Follows the format: `YYYY-MM-DD`.
	`policy_code`	Specifies the cancellation policy (override) code.	integer	To see the list of cancellation and prepaymeny policy codes at Booking.com, see cancellation and prepayment polices.
>>>> `guarantee_payment_policy`		Contains the guarantee payment details.	object
>>>>> `guarantee_payment`		Contains the guarantee payment details.	object
	`policy_code`	Specifies the cancellation policy code that has the guarantee payment details.	integer	For a full list of all the available cancellation codes, see the cancellation policy codes.
	`effective_from`	Specifies when the guarantee payment is charged.	enumerated string	Possible values are: - `after_reservation_is_made` - Enforces guests to make a payment immediately after reservation. - `after_free_cancellation_ends`: Enforces guests to make a payment after the free cancellation window has closed.
	`required`	Specifies whether a guarantee payment is mandatory.	boolean	Possible values are: - `1`: Guarantee payment required - `0`: Guarantee payment is not required
>>>> `pricing`		Contains the pricing details.	object	Only available when you enable the feature: Include products extra info (`include_extra_info_room_rates`) using the Provider portal.
	`type`	Specifies the pricing type.	enumerated string	Possible values are: - Standard - RLO - OBP - LOS
	`price1`	Specifies whether the roomrate accepts a single occupancy price.	boolean	Possible values are: 1 - Accepts single occupancy price 0 - Does not support single occupancy price.
>>>>> `occupancy`		Contains the occupancy details.	object
	`persons`	Specifies the number of occupants.	integer
	`percentage`/`additional`	Specifies the pricing as a percentage of the base price or as an additional amount from the base price.	integer	For example, if the base price is 200 and the price for 2 occupants is specified as a percentage = 95, then the price for 2 is 90. (95% of 200). Whereas, an `additional = -15`, means the price for 2 occupants is 185.
	`round`	Specifies the number of digits to round off.	integer
`ruid`		Specifies the unique ID of the request.	string	You can send this ID to Booking.com customer support if you run into an issue. This can help to understand what went wrong.

Is this page helpful? Yes | No