> 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/direct-connect-demand-push/interface-specifications-ari-service/operation-ari-update/faq.md).

# FAQ

**Invalid Credentials and Codes**:

* **Invalid Username/Password**:
  * If the `HotelARIUpdateRQ` contains an invalid Username/Password, the partner should return an error response with `ShortText="Invalid Username or Password"`.
* **Invalid HotelCode**:
  * If the `HotelARIUpdateRQ` contains an invalid HotelCode, the partner should return an error response with `ShortText="Invalid HotelCode"`.
* **Invalid RoomTypeCode or RatePlanCode**:
  * If the `HotelARIUpdateRQ` contains an invalid RoomTypeCode or RatePlanCode, the partner should return an error response with `ShortText="Invalid Room/Rate"`.

**XML Attributes**:

* **Request and Response XML**:
  * Will always contain an attribute `xmlns="http://cgbridge.rategain.com/OTA/2012/05"` at the root element.
* **Date Format**:
  * The date format for Start and End is always `YYYY-MM-DD`.

**Partial Update**:

* **Mandatory Support**:
  * OTA must support Partial Update, which means each attribute (i.e., Availability, rates, restrictions, or inventory) should be updated by API individually.
  * Partial update is mandatory, and existing values should not be impacted; only updated values should be impacted.
  * **Example**:
    * If a hotel is managing occupancy pricing for 1 Adult, 2 Adults, 3 Adults, etc., the API should update each individual occupancy price without impacting other occupancy-based pricing.
    * If the 1 Adult price is sent for a date, the API should only update the 1 Adult price while the pricing for 2 Adults and 3 Adults should remain the same with existing values.


---

# 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/direct-connect-demand-push/interface-specifications-ari-service/operation-ari-update/faq.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.