> 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/unavailable-properties.md).

# Unavailable Properties

If a requested property is unavailable, a **Property** element is returned with the **AvailabilityStatus** set to “Closed.” This element will also include the **ClosedReason** attribute, which indicates the reason for the closure.

Additionally, an **Error** element is returned, often providing further details. The **ResponseDataPath** attribute within the **Error** element will reference the specific property ID related to the issue.

Below is an example response for a request involving three properties, where one is unavailable (edited for clarity):

```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-09- 07T08:13:36.688+00:00" Success="true"
TotalProcessTime="228"/>
</Route>
<Error Code="IND12" Description="CTA RESTRICTION ON IN DATE"
ResponseDataPath="Hotel/Property@Code='XX;1111'" Type="Process"/>
</Head>
<Property xml:lang="en" AvailabilityStatus="Closed" ClosedReason="Unavailable" Code="XX;1111" />
<Property xml:lang="en" Code="XX;2222" AvailabilityStatus="Open">
... Room & Rate Details ....
</Property>
<Property xml:lang="en" Code="XX;3333" AvailabilityStatus="Open">
... Room & Rate Details ....
</Property>
</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.