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

# OTA\_ResRetrieveRS

**Reservation Retrieval:**

* **OTA\_ReadRQ**: PMS sends this message to request new reservations.
* **OTA\_ResRetrieveRS**: RGBridge responds with this message, providing the list of new reservations.
  * **SOAP Fault**: If a SOAP level fault occurs, a SOAP fault message will be sent instead.

**Response Messages**:

* If there are no new reservations, the `OTA_ResRetrieveRS` message will be returned without a `ReservationsList` node.
* If there are reservations waiting to be delivered, the `OTA_ResRetrieveRS` message will include a `ReservationsList` node containing one or more reservation messages.
  * **Configuration Setting**: The maximum number of reservations per message is limited by a configuration setting.
  * **@MoreIndicator Attribute**: If more reservations are waiting, this attribute will be set to true.

**PMS Processing**:

* The PMS should process the reservations downloaded and send an `OTA_NotifReportRQ` message indicating the processing results.
  * Typically, PMS confirmation numbers are returned for each reservation downloaded.
* PMS should process the reservations and send `OTA_NotifReportRQ` messages as required before sending further `OTA_ReadRQ` messages to avoid duplicate retrieval.

**ReservationsList Node**:

* Contains a list of `HotelReservation` nodes.
* The schema of the `HotelReservation` node is the same as described in the push model specification and is not detailed here.
* **Reference**: Please refer to the RGBridge Integration Specification document for additional details.

**Reservation retrieval response; Sample XML**

```xml
<OTA_ResRetrieveRs xmlns="http://www.opentravel.org/OTA/2003/05"  
            EchoToken="354"  
            TimeStamp="2011-01-26T10:22:00-05:00"  
            Target="Production"  
            Version="6.002" 
            MoreIndicator="true" > 
  <Success /> 
  <ReservationsList> 
    <HotelReservation> 
      <!-- details omitted --> 
    </HotelReservation> 
  </ReservationsList> 
</OTA_ReadRQ> 
```


---

# 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/ota_resretrievers.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.
