# Response message format.

<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> </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/Brand</p></td><td> </td><td><p> </p><p>0..M</p></td><td> </td><td> </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 6</p></td><td><p> </p><p>Brand code</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Name</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Brand name</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Token</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Token generated by UltraDirect</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Type</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Enum</p></td><td><p> </p><p>The XML schema has values “Chain” and “Independent” but actual value will be “Chain” in this context.</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>ModifyReservation</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Boolean</p></td><td><p> </p><p>Indicates whether the brand supports the ModifyReservation transaction</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>SessionControl</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Boolean</p></td><td><p> </p><p>Indicates whether the brand supports session control</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Brand/Email</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>Address</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Brand’s email address</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Brand/Media</p></td><td> </td><td><p> </p><p>0..M</p></td><td> </td><td><p> </p><p>Media information – i.e. the brand’s logo.</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Link</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Link to the media file</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Type</p></td><td><p> </p><p>0..1</p></td><td><p> </p><p>Enum.</p></td><td><p> </p><p>Type of media. Normally “Logo” for the brand logo.</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>MIME</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Media type, such as “image/jpeg” or “image/gif”</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/reference-data-transactions/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.
