> 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/rate-change-notification.md).

# Rate Change Notification

This operation enables the PMS to request RG Bridge to update OTAs with changes in rates. Here's a breakdown of the process:

1. **Triggering Rate Changes**: Rate changes in the PMS can occur through daily rate changes, creation of new rate plans, addition of new inventory to existing rate plans, or due to enabling a hotel for integration, rolling refresh, re-status, etc.
2. **Notification Messages**: In all these scenarios, the PMS should send notification messages for the products and date ranges affected using the `OTA_HotelRateAmountNotifRQ` message.
3. **Message Handling by RG Bridge**:
   * RG Bridge will store the message before sending it to all managed channels.
   * RG Bridge will send a success or failure message back to the PMS interface.
4. **Retry Mechanism**: In case of failures on the RG Bridge side, the PMS interface must retry the message transmission up to 5 times before marking the notification as a failure.
5. **Message Exchange**:
   * **Request**: `OTA_HotelRateAmountNotifRQ`
   * **Response**: `OTA_HotelRateAmountNotifRS`

<figure><img src="/files/XLi6gZ2vtsIHfstd8Fk5" alt=""><figcaption></figcaption></figure>


---

# 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/interface-specifications-availability-and-rates-notification-service/operations/rate-change-notification.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.