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

# RG Bridge - Reservation Retrieval (Pull)

This document is a part of the RGBridge Integration Deck, which provides comprehensive information on integrating RG Bridge with CRS or PMS systems. Here's an overview:

**RGBridge Integration Deck**:

* **Purpose**: To facilitate the integration of RG Bridge with CRS or PMS systems.
* **Integration**: RGBridge is the integrated version of RateGain's channel-management solution, trusted by the world’s leading hotels.
* **Flagship Product**: RG Channel Manager is the flagship product of RateGain, bringing smart technology to the global hospitality industry.

**Technical Specifications**:

* **Web Service Clients**: This document provides technical specifications for developing web service clients to pull reservations from RGBridge.
* **Supplementary Document**: This document should be read in conjunction with the RGBridge Integration Specification document for a complete understanding.


---

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