# Request 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/Process</p></td><td> </td><td><p> </p><p>1</p></td><td> </td><td> </td></tr><tr><td valign="top"> </td><td><p> </p><p>DataPath</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Set to "/HotelML/Form/BrandInformation”</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Function</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Set to “TI_BrandInformationV1_1”</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Token</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char</p></td><td><p> </p><p>Unique ID for the transaction generated by the system sending the transaction.</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Head/Route</p></td><td> </td><td><p> </p><p>1</p></td><td> </td><td> </td></tr><tr><td valign="top"> </td><td><p> </p><p>Source</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char 2-3</p></td><td><p> </p><p>Identifies the organization sending the transaction. The value to use will be provided during the implementation project.</p></td></tr><tr><td valign="top"> </td><td><p> </p><p>Destination</p></td><td><p> </p><p>1</p></td><td><p> </p><p>Char 2</p></td><td><p> </p><p>Always set to “00” (i.e. zero zero).</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Form/BrandInformation</p></td><td> </td><td><p> </p><p>1</p></td><td> </td><td><p> </p><p>Send this element without any Brand child elements to information on all brands.</p></td></tr><tr><td valign="top"><p> </p><p>HotelML/Form/BrandInformation/ Brand</p></td><td> </td><td><p> </p><p>0..M</p></td><td> </td><td><p> </p><p>If specific brands are required (rather than all brands) then this element should be repeated for each brand.</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 6</p></td><td><p> </p><p>Brand code</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/request-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.
