> 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/operations/reservation-notification/ota_hotelresnotifrs.md).

# OTA\_HotelResNotifRS

**PMS Response**:

* The PMS should respond to the `OTA_HotelResNotifRQ` message by returning an `OTA_HotelResNotifRS` message.
* **Exception**: If a REST level fault occurs while the PMS processes the request, a REST fault should be generated and returned. This indicates that the message does not meet the web service specifications. RG Bridge can receive and process REST faults.

**Validation**:

* If the PMS is not able to validate a message at the application level, it should still return an `OTA_HotelResNotifRS` message.

**Synchronous Communication**:

* Since synchronous communication mode is used, the PMS should be able to process the message and return either:
  * A confirmation number (success).
  * An error response (failure).

**Error Handling**:

* Response messages indicating failures should contain at least one error element.
* It is possible that more than one error element may be returned.

**Response indicating success**

```xml
<OTA_HotelResNotifRS  TimeStamp="2004-04-14T09:42:26"> 
 
<HotelReservations> 
 
<HotelReservation> 
 
<ResGlobalInfo> 
 
<HotelReservationIDs>  
<HotelReservationID ResID_Type="3" ResID_Value="123456789" /> 
 
<HotelReservationID ResID_Type="14" ResID_Value="chd23242342" 
/> 
 
</HotelReservationIDs> 
 
</ResGlobalInfo> 
 
</HotelReservation> 
 
</HotelReservations> 
 
<Success /> 
 
</OTA_HotelResNotifRS> 

```

**Response indicating failure**

```xml
<OTA_HotelResNotifRS EchoToken="RG1232" TimeStamp="2004-04-14T09:42:26"> 
 
<Errors> 
 
<Error Code="3001" Status="NotProcessed" 
 
ShortText="Invalid Rate" />  
</Errors> 
 
</OTA_HotelResNotifRS> 

```


---

# 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/operations/reservation-notification/ota_hotelresnotifrs.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.
