Single property availability

Summary and examples

This transaction is used to determine which rooms and rates are available at a one property. It was developed before the Enhanced Shopping Transaction (EST) and has very similar functionality. The only differences are:

  • The transaction only returns rate and availability information for one property (EST supports up to 200).

  • The transaction does not support user-specified timeouts or multipart responses (this is only relevant for EST, which has responses for many properties)

  • If a property is unavailable, an error will be returned (such as “PID10”) but in the EST transaction, the Property element will be returned with an AvailabilityStatus of “Closed” ( a warning may also be returned to provide additional information).

As this transaction is so similar to the EST transaction, please refer to section 0 for full details of all the rate and availability features.

Simple Usage Example

The example shows a simple request message, with no specific rates are requested.

<HotelML xmlns="
http://www.xpegs.com/v2001Q3/HotelML
">
<Head>
<Process DataPath="/HotelML/Form/PropertyInformation" Function="TI_PropertyInformationV1_1" Token="1307007312118"/>
<Route Destination="00" Source="01"/>
</Head>
<Form>
<PropertyInformation PropertyCode="MC;NYCMQ">
<PropertyRate NumberOfAdults="2" NumberOfBeds="1" NumberOfRooms="1">
<DateRange InDate="2011-07-01" OutDate="2011-07-04"/>
</PropertyRate>
</PropertyInformation>
</Form>
</HotelML>

The following response includes information about the available room and rates. The amount of information returned in this example is fairly basic – other hotels will return more detailed information.

No Availability Example

The following is an example response for a property that has no availability for the specified criteria:

Requested Language Example

It is possible to request the room, rate and policy descriptions (from the hotel’s CRS) to be returned in a specific language. An example of requesting a response in German is shown below:

An example response is shown below.

If the room rate information in the hotel’s CRS is not available in the requested language, the hotel should return their room rate descriptions in English and indicate that in the language indicator field being returned to the affiliate.

The following example shows a response to a request for Spanish (“es”). The room rate descriptions are not available in Spanish and so are returned in English.

There is one exception to the above rule, which is that if the affiliate is configured to accept response messages in ‘unmatched’ languages (i.e. not the requested language or English) then the response will be in whichever language the hotel’s CRS has provided. The language returned will be indicated in the response using the XML: lang attribute.

If the affiliate decides not to support this option (it is configurable by RateGain), any time a hotel responds with a language indicator that does not match the requested language code or is not English, an error message will be returned. An example is below:

PreviousResponse message format..NextRequest message format

Last updated