search

Rate Rules

This transaction set is used to request additional policy information for a specific rate and room type combination that is not included in the availability response. All hotel CRSs support this transaction, however, each CRS operates differently and may or may not include all optional fields.

hashtag
Example Rate rules request:

<HotelML xmlns="
http://www.xpegs.com/v2001Q3/HotelML
">
<Head>
<Process DataPath="/HotelML/Form/PropertyInformation" Function="TI_PropertyInformationV1_1" Token="1311082860417"/>
<Route Destination="00" Source="XX"/>
</Head>
<Form>
<PropertyInformation PropertyCode="HY;998">
<PropertyRate NumberOfAdults="2" NumberOfChildren="1" NumberOfRooms="1">
<AgentInfo Number="XXXXXXXX" Type="TIDS"/>
<RatePlan Code="RACK" InDate="2013-10-10" OutDate="2013-10-11">
<RoomType Code="KNG"/>
</RatePlan>
</PropertyRate>
</PropertyInformation>
</Form>
</HotelML>

  • This request should NOT be used to check availability.

  • There is a maximum of 1 PropertyInformation element (brand;pid) that can be included in each request.

  • Rate Rule requests are used if more detailed information on the rate is required or if rate change details are required and not returned in the EST response.

  • This request is mandatory for public/commissionable rates.

hashtag
Example Rate Rules response:

  • All relevant textual policies will need to be displayed for public rates but may not be needed for negotiated rates.

  • Except TaxDetail information, most policy information returned in the Rate Rules response is unstructured free-form description rather than structured coded and formatted responses.

  • Confirm availability by running an enhanced shopping request using RequestedAccuracy=SourceOnly between rate rules and book reservations.

PreviousEST (Enhanced Shopping Transaction)NextBook Reservation

Last updated