← Step 3 – Create room type | Step 5 – Create product →¶
Step 4 – Create rate plan¶
You have now specified your basic property information and one room type. The next step is to create a rate plan.
Rate plans contain very little information. They don't even contain a room price. The only purpose of a rate plan is to link a room type to a sellable product. Don't worry if this is confusing: you'll learn more about products later.
Use this method and URL to create a new rate plan:
POST https://supply-xml.booking.com/hotels/ota/OTA_HotelRatePlanNotifAs usual, the sample request below contains {PlaceHolders}.
Sample request¶
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelRatePlanNotifRQ
xmlns="http://www.opentravel.org/OTA/2003/05"
MessageContentCode="8"
Version="1.005"
Target='Test'>
<!-- Replace the {PlaceHolder} in the following line! -->
<RatePlans HotelCode="{PropertyID}">
<RatePlan RatePlanNotifType="New">
<Description Name="Basic rate 2 guests"/>
</RatePlan>
</RatePlans>
</OTA_HotelRatePlanNotifRQ>This request creates one new rate plan, containing a name and not much else. We'll explain its purpose soon.
Sample response¶
A successful response includes a RatePlanCrossRef[@ResponseRatePlanCode] attribute containing the rate plan ID:
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelRatePlanNotifRS 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_HotelRatePlanNotifRS.xsd" TimeStamp="2018-02-09T13:14:28+00:00" Target="Test" Version="3.000">
<RatePlanCrossRefs>
<RatePlanCrossRef ResponseRatePlanCode="10858982"/>
</RatePlanCrossRefs>
<Success />
</OTA_HotelRatePlanNotifRS>
<!-- RUID: [UmFuZG...] -->Learn more about the last call here: OTA_HotelRatePlanNotif