> 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/xml-usage-specification.md).

# XML Usage Specification

| <p><strong>Element/@Attribute</strong></p><p> </p><p><strong>Parent XPath</strong></p> | <p> </p><p><strong>Description</strong></p>                                                                                                                                                                   | **Occurrences** |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
| <p>@TimeStamp </p><p><strong>/OTA\_HotelRateAmountNotifRS</strong></p>                 | <p> </p><p>Time of the transaction in XML schema date-time format</p>                                                                                                                                         | 1               |
| <p>@EchoToken</p><p> <strong>/OTA\_HotelRateAmountNotifRS</strong></p>                 | Unique identifier to track RQ/RS message                                                                                                                                                                      | 1               |
| <p>@Target</p><p><strong>/OTA\_HotelRateAmountNotifRS</strong></p>                     | Always set to “Production”                                                                                                                                                                                    | 1               |
| <p>@Version</p><p> <strong>/OTA\_HotelRateAmountNotifRS</strong></p>                   | <p> </p><p>Always set to “1.0”</p>                                                                                                                                                                            | 1               |
| <p> Success</p><p><strong>/OTA\_HotelRateAmountNotifRS</strong></p>                    | <p>If included this element will indicate that</p><p>the request message was successfully processed.</p><p><br></p><p>Either a Success element or Errors/error element(s) are required in every response.</p> | 0..1            |
| <p>Errors</p><p><strong>/OTA\_HotelRateAmountNotifRS</strong></p>                      | Either a Success element or Errors/error element(s) are required in every response.                                                                                                                           | 0..1            |
| <p>Error</p><p><strong>/OTA\_HotelRateAmountNotifRS /Errors</strong></p>               | <p>Description of cause for a fatal problem during request message processing.</p><p>\*If an Errors element is included one or more Error elements are required</p>                                           | 1               |
| <p> @Type</p><p><strong>/OTA\_HotelRateAmountNotifRS /Errors/Error</strong></p>        | This is an enumeration of HTNG approved error types (OTA code list EWT). See the appendix for supported values.                                                                                               | 1               |
| <p>@Code</p><p><strong>/OTA\_HotelRateAmountNotifRS /Errors/Error</strong></p>         | This is an enumeration of HTNG approved error codes (OTA code list ERR). See appendix for supported values.                                                                                                   | 1               |


---

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

```
GET https://developer.rategain.com/our-products/channel-manager/rg-bridge-supply-push/interface-specifications-availability-and-rates-notification-service/operations/rate-change-notification/xml-usage-specification.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.