# HotelARIUpdateRS

**Response Message**:

* **HotelARIUpdateRS**:
  * OTA should respond to the `HotelARIUpdateRQ` request by sending a `HotelARIUpdateRS` message.
  * If the OTA is not able to validate a message at the application level, it should still return a `HotelARIUpdateRS` message.

**Validation and Errors**:

* Response messages indicating failures must contain at least one error element. It is possible to return more than one error element.
* **Update Failure**: If any of the requested updates cannot be completed successfully, the OTA must ensure that no update is made to ARI information at all.

**Successful Update**:

* After updating the ARI information, the OTA should:
  * Return a `HotelARIUpdateRS` message with a single Success element.

| <p><strong>Element/@Attribute</strong></p><p><strong>Parent XPath</strong>  </p> | <p>  </p><p><strong>Description</strong> </p>                                                                                                                                                                                                                         | **Mandatory**                    |
| -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
| <p>@TimeStamp </p><p><strong>/HotelARIUpdateRS</strong>  </p>                    | <p>  </p><p>Time of the transaction in XML schema date-time format. </p>                                                                                                                                                                                              | Y                                |
| <p>@Version </p><p><strong>/HotelARIUpdateRS</strong>  </p>                      | <p>  </p><p>For this version of the specification set to “1.0” </p>                                                                                                                                                                                                   | Y                                |
| <p>  Success </p><p><strong>/HotelARIUpdateRS</strong>  </p>                     | <p>If included, this element will indicate that the request message was successfully processed. </p><p>If this element is returned, a Products element must also be returned. Either a Success element or an</p><p>Errors element is required in every response. </p> | <p><br> Y? </p>                  |
| <p>Errors </p><p><strong>/HotelARIUpdateRS</strong></p>                          | <p>If included, this element will indicate that the request message could not be processed. </p><p>Either a Success element or an Errors element is required in every response. </p>                                                                                  | <p>Y? </p><p><br></p><p><br></p> |
| <p>Error </p><p><strong>/HotelARIUpdateRS/Errors</strong>  </p>                  | <p>Description of cause for a fatal problem during request message processing. </p><p>\*If an Errors element is included, at least one Error element is required. </p>                                                                                                | Y                                |
| <p>@Type </p><p><strong>/HotelARIUpdateRS/Errors/Error</strong>  </p>            | <p>  </p><p>This is an enumeration of error types. </p><p>See the appendix for supported values. Code list Error types. </p>                                                                                                                                          | Y                                |
| <p>@Code </p><p><strong>/HotelARIUpdateRS/Errors/Error</strong>  </p>            | <p>  </p><p>This is an enumeration of error codes. </p><p>See the appendix for supported values. Code list Error Codes. </p>                                                                                                                                          | Y                                |


---

# Agent Instructions: 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:

```
GET https://developer.rategain.com/our-products/channel-manager/direct-connect-demand-push/interface-specifications-ari-service/operation-ari-update/hotelariupdaters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.