> 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/ota_hotelrateamountnotifrq.md).

# OTA\_HotelRateAmountNotifRQ

The PMS should use the `OTA_HotelRateAmountNotifRQ` message to send rate updates. These updates must be sent at the product level, ensuring accurate and comprehensive communication of rate changes.

**Rate change request XML sample for Base Rate (Room price)**

```xml

<OTA_HotelRateAmountNotifRQ xmlns="
http://www.opentravel.org/OTA/2003/05

"
 
TimeStamp="2011-10-01T12:00:00"
Target="Production"
EchoToken="235651837sddge4"
Version="1.002">
 <RateAmountMessages HotelCode="ATLPE">
 <RateAmountMessage>
     <StatusApplicationControl  Start="2011-12-01" 
                                End="2011-12-01"


                                 RatePlanCode="BARA00"


                                 InvCode="STD"/>
       <Rates>


         <Rate CurrencyCode="USD">


           <BaseByGuestAmts>


             <BaseByGuestAmt AmountBeforeTax="100.00"
AmountAfterTax="120.00"/>
           </BaseByGuestAmts>
         </Rate>
       </Rates>
 </RateAmountMessage>
 </RateAmountMessages>
</OTA_HotelRateAmountNotifRQ>
```

###

**Rate change request XML sample for Occupancy Rate**

```xml
<OTA_HotelRateAmountNotifRQ xmlns="
http://www.opentravel.org/OTA/2003/05

"

TimeStamp="2011-10-01T12:00:00"
EchoToken="235651837sddge4"
Target="Production"
Version="1.002">
 <RateAmountMessages HotelCode="ATLPE">
 <RateAmountMessage>
     <StatusApplicationControl  Start="2011-12-01"
                                End="2011-12-01"
                                RatePlanCode="BARA00"
                                InvCode="STD"/>
      <Rates>
        <Rate CurrencyCode="USD">
          <BaseByGuestAmts>
            <BaseByGuestAmt AgeQualifyingCode="10" NumberOfGuests="1"
AmountBeforeTax="100.00" AmountAfterTax="120.00"/>
<BaseByGuestAmt AgeQualifyingCode="10" NumberOfGuests="2"
AmountBeforeTax="120.00" AmountBeforeTax="144.00"/>
          </BaseByGuestAmts>
<AdditionalGuestAmounts>
<AdditionalGuestAmount  AgeQualifyingCode="10" Amount="80"/>
<AdditionalGuestAmount AgeQualifyingCode="8" Amount="50"/>
</AdditionalGuestAmounts>
       </Rate>
      </Rates>
 </RateAmountMessage>
 </RateAmountMessages>
</OTA_HotelRateAmountNotifRQ>
```


---

# 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/ota_hotelrateamountnotifrq.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.