> 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/channel-manager/rg-bridge-reservation-retrieval-pull/operations/reservation-retrieval/xml-usage-specification-1.md).

# XML Usage specification

| <p><strong>Element/@Attribute</strong></p><p><strong>Parent XPath</strong></p>      | **Description**                                                                                                                                                                |
| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>@TimeStamp</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                        | Time of the transaction in xml schema date-time format                                                                                                                         |
| <p>@Version</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                          | The OTA schema version. Mandatory. Use “6.002”.                                                                                                                                |
| <p>@Target</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                           | Set to “Production”.                                                                                                                                                           |
| <p>@MoreIndicator</p><p><br></p><p><strong>/OTA\_ResRetrieveRS</strong></p>         | Set to true if there are more reservations to be downloaded. This happens when the number of reservations in a message is limited by configuration setting.                    |
| <p>Errors</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                            | Included in response only if there are errors in processing                                                                                                                    |
| <p>Error</p><p><strong>/OTA\_ResRetrieveRS/Errors</strong></p>                      | <p>Response will include as many Errors as required. At least one Error element must be present if the response contains</p><p>Errors.</p>                                     |
| <p>@Type</p><p><strong>/OTA\_ResRetrieveRS/Errors/Error</strong></p>                | Error type. Should be one of the codes listed in Error Types below.                                                                                                            |
| <p>@Code</p><p><strong>/OTA\_ResRetrieveRS/Errors/Error</strong></p>                | Error code. Should be one of the codes listed in Error Codes below.                                                                                                            |
| <p>@ShortText</p><p><strong>/OTA\_ResRetrieveRS/Errors/Error</strong></p>           | Free Text                                                                                                                                                                      |
| <p>@Status</p><p><strong>/OTA\_ResRetrieveRS/Errors/Error</strong></p>              | Should be set to String “*NotProcessed*”                                                                                                                                       |
| <p>Success</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                           | Presence of this element indicates a successful Response and in case of a Success response the Errors element should not be present.                                           |
| <p>Warnings</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                          | Response may include warnings along with a Success response. Warnings are not allowed with a response that contains Errors.                                                    |
| <p>Warning</p><p><strong>/OTA\_ResRetrieveRS/Warnings</strong></p>                  | Response may include as many warning as required. At least one Warning element must be present in a response that contains Warnings.                                           |
| <p>@Code</p><p><strong>/OTA\_ResRetrieveRS/Warnings/Warning</strong></p>            | The error code.                                                                                                                                                                |
| <p>@ShortText</p><p><strong>/OTA\_ResRetrieveRS/Warnings/Warning</strong></p>       | Free Text                                                                                                                                                                      |
| <p>ReservationsList</p><p><strong>/OTA\_ResRetrieveRS</strong></p>                  | Container for reservations. Not present if the response contains Errors. Also not present if there are no reservations to be delivered.                                        |
| <p>HotelReservation</p><p><strong>/OTA\_ResRetrieveRS/ReservationsList</strong></p> | Reservation record. Please refer to RGBridge Integration specification document for details. The @ResStatus attribute of this node will contain the status of the reservation. |


---

# 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/channel-manager/rg-bridge-reservation-retrieval-pull/operations/reservation-retrieval/xml-usage-specification-1.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.