> 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/information-data-flow/information-delivery-mechanism.md).

# Information delivery mechanism

**Push Delivery**\
The integration will primarily operate on a PUSH mechanism:

* **ARI Updates**: The PMS/CRS will PUSH ARI (Availability, Rates, and Inventory) data to RG Bridge, which will then distribute it to all OTAs.
* **Reservations**: RG Bridge will receive reservations from OTAs and PUSH them to the CRS/PMS.

**Real-Time vs. Batch Processing**\
RG Bridge processes all data in real-time, and the partner is expected to handle data in real time as well.

* If real-time processing is not feasible due to technical or business constraints, batch updates can be provided. However, this will incur additional costs.


---

# 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/information-data-flow/information-delivery-mechanism.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.