# Response message format

The response message is almost identical to the Enhanced Shopping (EST) Response and is only summarized here.

<table data-header-hidden><thead><tr><th valign="top">Element Path</th><th>Attribute</th><th>Occ</th><th>Type</th><th>Notes</th></tr></thead><tbody><tr><td valign="top"><p> </p><p>HotelML/Head</p></td><td> </td><td><p> </p><p>1</p></td><td> </td><td><p> </p><p>This is the standard element containing some transaction metadata and any applicable errors or warnings. For details of this element and all child elements- see Section 0, header (Response Message)</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Property</p></td><td> </td><td><p> </p><p>0..1</p></td><td> </td><td> </td></tr><tr><td valign="top"> </td><td><p> </p><p>xml:lang</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Identifies the language of the response message that was returned by the hotel’s CRS.</p><p> </p><p>The language will normally be requested language or English if the requested language was not available. However, if the affiliate is configured to accept response messages with unmatched languages, RateGain will</p><p>return the response to the affiliate in whichever language the hotel’s CRS</p><p>has provided</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Code</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Chain and property code, separated by a semi-colon – e.g. “UI;AB1234”</p></td></tr></tbody></table>

<br>

&#x20;

&#x20;

&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"> </td><td valign="top"><p> </p><p>DataOrigin</p></td><td valign="top"><p> </p><p>0..1</p></td><td valign="top"><p> </p><p>Enum.</p></td><td valign="top"><p> </p><p>Indicates whether the response was generated from the UltraDirect transaction cache or the source (CRS). Values are: “Cache” or “Source”. Only returned Head/Route/@RequestedAccuracy is supplied in the request</p></td></tr><tr><td valign="top"> </td><td valign="top"><p> </p><p>DataAge</p></td><td valign="top"><p> </p><p>0..1</p></td><td valign="top"><p> </p><p>Date &#x26;</p><p>time</p></td><td valign="top"><p> </p><p>The date and timestamp of the response. If the response was generated from the cache then this is the timestamp of when it was added to the cache). The format is “2011-05-08T14:28:01.268-00:00”. Only returned Head/Route/@RequestedAccuracy is supplied in the request</p></td></tr><tr><td valign="top"> </td><td valign="top"><p> </p><p>Token</p></td><td valign="top"><p> </p><p>0..1</p></td><td valign="top"><p> </p><p>Char</p></td><td valign="top"><p> </p><p>Token generated by UltraDirect</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Property/Rate</p></td><td valign="top"> </td><td valign="top"> </td><td valign="top"> </td><td valign="top"><p> </p><p>This is exactly the same as the rate information returned in Enhanced Shopping transaction and so is not repeated here. See section 0 for details of this element and all child elements.</p></td></tr></tbody></table>


---

# 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/ultradirect/ultradirect-transaction-sets-xml/single-property-availability/response-message-format.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.