search
Ctrlk

UltraDirect Cache Processing

The UltraDirect Availability Cache functionality allows rate and availability information for properties to be retrieved in the EST response. Cached single-property availability responses can be utilized by UltraDirect to generate multi-property availability responses, and vice versa.

The RequestedAccuracy attribute within the Route element in the message header specifies whether the cache should be used. Affiliates can indicate their preference for responses to be sourced either from the cache or directly from the source (e.g., the hotel’s CRS).

In the example below, the affiliate specifies that responses can be retrieved from either the cache or the source:

<HotelML xmlns="http://www.xpegs.com/v2001Q3/HotelML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Head>
<Process DataPath="/HotelML/Form/MultiAvailability" Function="TI_MultiAvailabilityV1_1"
Token="1285940187599"/>
<Route Destination="00" Source="01" RequestedAccuracy="CacheOrSource"/>
</Head>
<Form>
<MultiAvailability>
<Property Code="UI;12345"/>
<Property Code="UI;54321"/>
<RateCriteria VersionCompliance="Enhanced_V1" MatchingQualifier="ExactAndPublic"
NumberOfBeds="2" BedType="Queen" NumberOfRooms="1" RoomCategory="Standard">
<GuestCount Type="Adult" Count="1"/>
<GuestCount Type="Child" Count="1" Age="14"/>
<GuestCount Type="Child" Count="1" Age="1"/>
<ExtraBed Type="Crib" Number="1"/>
<DateRange InDate="2010-07-01" OutDate="2010-07-05"/>
<RateSearch RatePlanCode="RAC" RatePlanType="Standard"/>
<RateSearch RatePlanCode="PRO" RatePlanType="Standard"/>
</RateCriteria>
</MultiAvailability>
</Form>
</HotelML>

The response message specifies, for each property, whether the information was retrieved from the cache or directly from the source. It also provides the "age" of the response by including a timestamp indicating when the response was created.

  • If the information was returned from the cache, the age corresponds to the timestamp of when the response was initially added to the cache.

  • If the information was sourced directly, the timestamp reflects when the response was generated in real-time.

Note:

As a general practice, for EST API transactions, “CacheOrSource” is used.

An example is shown below:

If the requested accuracy is not available for a requested property then the Property element is returned with AvailabilityStatus set to “Unknown”. For example, if the previous request message was changed so that RequestedAccuracy=”CacheOnly” and there is no matching transaction in the cache for property UI;54321 then the response would be as follows:

Last updated