4.6. BaseRates¶
If the action parameter is OTA_HotelRatePlan:BaseRates, the client sends a pull request to query rate plans from the server in order to import data back into a PMS or portal.
4.6.1. Client request¶
The parameter request contains an OTA_HotelRatePlanRQ document.
Nested inside one RatePlan element the following sub-elements are given in order:
-
Zero or one DateRange element with Start and End attributes.
-
Zero or more RatePlanCandidate elements with attributes RatePlanCode and RatePlanID.
-
One HotelRef element with attributes HotelCode and HotelName - the rules are the same as for room availability notifications (section 4.1.1).
Here is an example:
|
|
Regarding DateRange and RatePlanCandidate six cases need to be distinguished:
-
DateRange omitted, RatePlanCandidate present:
The server will answer with the matching rate plans.
-
DateRange omitted, RatePlanCandidate omitted:
The server will answer with all the rate plans it has on record. Note that the Rate elements are omitted, the response contains just the RatePlan elements with the Description whose Name attribute is set to
Title. -
DateRange empty, RatePlanCandidate present:
If the server supports deltas, it must return the changes to the requested rate plans since the last request by the same client. If the server does not support deltas, this is not possible and will trigger a warning response.
-
DateRange empty, RatePlanCandidate omitted:
This is not possible and will trigger a warning response.
-
DateRange set, RatePlanCandidate present:
Server responds with all rates matching the given date range and rate plan.
-
DateRange set, RatePlanCandidate omitted:
The server response contains descriptions of the rate plans having rates in the given date range. Note that the Rate elements are omitted, the response contains just the RatePlan elements with the Description whose Name attribute is set to
Title.
4.6.2. Server response¶
The server will send a response indicating the outcome of the request. The response is a OTA_HotelRatePlanRS document. Any of the four possible AlpineBits® server response outcomes (success, advisory, warning or error) are allowed. See Appendix A for details.
In case of a successful outcome, the Success element is followed by a RatePlans element with the information about the hotel.
Here is an example:
|
|