> 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.md).

# XML Usage specification

| <p><strong>Element/@Attribute</strong></p><p><strong>Parent XPath</strong></p>                            | **Description**                                                              |
| --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| <p>@TimeStamp</p><p><strong>/OTA\_ReadRQ</strong></p>                                                     | Time of the transaction in xml schema date-time format                       |
| @Version **/OTA\_ReadRQ**                                                                                 | The OTA schema version. Mandatory. Use “3.500”.                              |
| @Target **/OTA\_ReadRQ**                                                                                  | Set to “Production”.                                                         |
| <p>POS</p><p><strong>/OTA\_ReadRQ</strong></p><p><strong>/OTA\_ReadRQ /POS</strong></p>                   | Element for indicating the source system.                                    |
| <p>RequestorID</p><p><strong>/OTA\_ReadRQ /POS/Source</strong></p>                                        | <p><br></p>                                                                  |
| <p>@Type</p><p><strong>/OTA\_ReadRQ /POS/Source/RequestorID</strong></p>                                  | Type of the ID. Set to “22”. ERSP (Electronic reservation service provider). |
| <p>@ID</p><p><strong>/OTA\_ReadRQ /POS/Source/RequestorID</strong></p>                                    | The id for the PMS.                                                          |
| <p>BookingChannel</p><p><strong>/OTA\_ReadRQ /POS/Source</strong></p>                                     | Requestor Name information                                                   |
| <p>@Type</p><p><strong>/OTA\_ReadRQ /POS/Source/BookingChannel</strong></p>                               | The type of the requestor system. “4” for PMS, “5” for CRS.                  |
| <p>@Primary</p><p><strong>/OTA\_ReadRQ /POS/Source/BookingChannel</strong></p>                            | Set to “true”.                                                               |
| <p>CompanyName</p><p><strong>/OTA\_ReadRQ /POS/Source/BookingChannel</strong></p>                         | Name of the requestor System.                                                |
| <p>@Code</p><p><strong>/OTA\_ReadRQ /POS/Source/BookingChannel</strong></p>                               | The code of the PMS, assigned by RateGain.                                   |
| <p>ReadRequests</p><p><strong>/OTA\_ReadRQ</strong> </p>                                                  | Container for the read request                                               |
| <p>HotelReadRequest</p><p><strong>/OTA\_ReadRQ/ReadRequests</strong></p>                                  | The read request                                                             |
| <p>@HotelCode</p><p><strong>/OTA\_ReadRQ/ReadRequests/HotelReadRequest</strong></p>                       | The hotel code of the hotel for which the reservation is to be downloaded.   |
| <p>SelectionCriteria</p><p><strong>/OTA\_ReadRQ/ReadRequests/ HotelReadRequest</strong></p>               | Contains the selection criteria to filter reservations to be retrieved.      |
| <p>@SelectionType</p><p><strong>/OTA\_ReadRQ/ReadRequests/HotelReadRequest/SelectionCriteria</strong></p> | Set to “Undelivered” to request all previously undelivered reservations.     |


---

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