> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/our-products/smart-distribution/multiavailability-enhanced-shopping-transaction/enhanced-shopping-est-detailed-rate-information/ultradirect-cache-processing.md).

# 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:

```xml
<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:

```xml
<HotelML xmlns="http://www.xpegs.com/v2001Q3/HotelML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Head>
<Route Destination="01" Source="00">
<Operation Action="Create" App="TIDispatcher" AppVer="1.12.40.2.8.1" DataPath="/HotelML" StartTime="2010-06-07T08:13:36.688+00:00" Success="true" TotalProcessTime="228"/>
</Route>
</Head>
<Property xml:lang="en" Code="UI;12345" DataAge="2011-06-30-02T09:27:04.173-00:00" DataOrigin="Cache" AvailabilityStatus="Open">
... Room & Rate Details ....
</Property>
<Property xml:lang="en" Code="UI;54321" DataAge="2011-06-30-08T14:28:01.268-00:00" DataOrigin="Source" AvailabilityStatus="Open">
... Room & Rate Details ....
</Property>
</HotelML>
```

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:

```xml
<HotelML xmlns="http://www.xpegs.com/v2001Q3/HotelML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Head>
<Route Destination="01" Source="00">
<Operation Action="Create" App="TIDispatcher" AppVer="1.12.40.2.8.1" DataPath="/HotelML" StartTime="2010-06-
07T08:13:36.688+00:00" Success="true" TotalProcessTime="228"/>
</Route>
<Error Code="CHE06" Description="RequestedAccuracy.CacheOnly - No cached data matching the requested criteria for
property: UI;54321" ResponseDataPath="Hotel/Property@Code=' UI;54321'"Type="Process"/>
</Head>
<Property xml:lang="en" Code="UI;12345" Token="1275898416589" DataAge="2010-06-30-08T14:28:01.268-00:00"
DataOrigin="Cache" AvailabilityStatus="Open">
... Room & Rate Details ....
<Property xml:lang="en" Code="UI;54321"Token="1275898416589" AvailabilityStatus="Unknown" />
</HotelML>
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.rategain.com/our-products/smart-distribution/multiavailability-enhanced-shopping-transaction/enhanced-shopping-est-detailed-rate-information/ultradirect-cache-processing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
