> 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-supply-push/integration-overview.md).

# Integration Overview

## **Purpose**

### Overview

This document outlines the integration process between a Central Reservation System (CRS) or Property Management System (PMS) and RateGain's channel management solution, known as RG Bridge. Throughout this document, CRS/PMS service providers are referred to as partners or third-party systems. The following sections detail the necessary steps and associated processes for a successful integration.

## **Objective**

The goal of the integration is to seamlessly send reservations from various inventory distribution channels to a hotel’s PMS system.

There are two main integration scenarios:

1. **RG Bridge integration with a CRS**: The CRS then sends the data to the PMS.
2. **RG Bridge integration directly with a PMS**: Reservations go straight to the PMS.

In both cases, the final destination for reservations is always the hotel’s PMS system. The two versions are illustrated below.

### RG Bridge integration with CRS    <a href="#objectiveofintegration-rgbridgeintegrationwithcrs" id="objectiveofintegration-rgbridgeintegrationwithcrs"></a>

### &#x20;                                                 <a href="#objectiveofintegration" id="objectiveofintegration"></a>

<figure><img src="https://3945324883-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fp4y5dHVBc6vTCuYBLiHH%2Fuploads%2F04FkXSSTo7IKPpbGwn2K%2F413603028.png?alt=media" alt=""><figcaption></figcaption></figure>

### RG Bridge integration with PMS <a href="#objectiveofintegration-rgbridgeintegrationwithpms" id="objectiveofintegration-rgbridgeintegrationwithpms"></a>

&#x20;                                                                  &#x20;

<figure><img src="https://3945324883-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fp4y5dHVBc6vTCuYBLiHH%2Fuploads%2FqV8HJQar9guWLqxls2o4%2F413603029.png?alt=media" alt=""><figcaption></figcaption></figure>

<br>

&#x20;                                                                   &#x20;

<br>


---

# 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-supply-push/integration-overview.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.
