> 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-availability-and-rates-notification-service/operations/points-to-remember.md).

# Points to remember

#### OTA\_HotelAvailNotifRQ Operation

**Usage**:

* The `OTA_HotelAvailNotifRQ` operation is used to send both Inventory (BookingLimit) and Restrictions (Arrival/Departure/Master Status/LOS restrictions/AdvPurchase) updates.
* Allocation/InventoryCount/BookingLimit is manageable at the room level only by a CRS/PMS partner.

**Separate Messages for Inventory and Restrictions**:

* If both inventory and restriction need to be updated for the same room type and date, two separate messages must be sent to the RG Bridge ARI service. Partners should implement this use case accordingly.

**Compact ARI Updates**:

* ARI updates for a range of dates should be prepared compactly, covering multiple days using `StartDate` and `EndDate` in a single element (i.e., `AvailStatusMessage` / `RateAmountMessage` block), if the same ARI data needs to be updated for a range of dates.

**Delta Updates Recommendation**:

* Partners should always send delta updates after a full refresh is made initially for a new hotel connected to the interface.
* Example: If a booking/cancellation is made for a particular HotelProduct (RoomType + RatePlan), partners should send updates for the corresponding HotelProduct and specific dates affected by the new booking/cancellation.
* It is not allowed to send updates for all HotelProducts or larger date ranges that are not part of the recent booking/cancellation received for a hotel.


---

# 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-availability-and-rates-notification-service/operations/points-to-remember.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.