> 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/interface-specifications-reservation-notification-service/rg-bridge-integration-process.md).

# RG Bridge integration process

The integration process should be well-planned and can be divided into the following phases:

**Phase 1: Initiation**

* **Technical Readiness Assessment**: Partners should assess their compatibility, resources, and know-how.
* **Pilot Hotel Selection**: A pilot hotel is usually agreed upon.
* **Test Account Setup**: Partners are provided with a test account and sufficient information to facilitate planned integration.
  * **Information Provided**:
    * Hotel Code and Hotel Name
    * List of products
    * Room type code
    * Rate type code
    * List of channels subscribed
    * OTA sell code and OTA name

**Phase 2: Development**

* **Development Kick-off**: Begin development with the provided information.
* **Integration Details**: Partners must provide technical descriptions and test results towards the end of this phase.

**Phase 3: Certification**

* **Test Plan**: Receive a test plan and test cases.
* **Certification**: Complete and sign off on the certification process.

**Phase 4: Production Pilot**

* **Pilot Monitoring**: Connect the pilot hotel to RG Bridge and monitor the integration to ensure success.

**Phase 5: Production**

* **Go Live**: Release the integration to production and make it generally available.


---

# 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/interface-specifications-reservation-notification-service/rg-bridge-integration-process.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.