> 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/rg-bridge-setup.md).

# RG Bridge Setup

For a seamless integration of RG Bridge with third parties, some essential customer information is required.

**Property Requirements Specifications (PRS)**:

* It's essential to fill out the PRS form with details about the property and its intended users.
* This form must be submitted to RateGain before the property goes live in production.

**RG Bridge with User Interface**:

* The RG Bridge includes a user interface for integrated properties, offering several benefits:
  * Monitor the accurate sending/receiving of data to/from the CRS/PMS.
  * Monitor the accurate sending/receiving of data to/from the OTA/channels.
  * Quickly troubleshoot failure points in case of errors.
  * Use an online web interface to check the status of your requests.


---

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