> 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/ultradirect/ultradirect-transaction-samples-and-usage.md).
# UltraDirect Transaction Samples and Usage
This document is designed to guide the client technical team through the Setup, Development, and QA phases of the implementation process as outlined in the diagram below.
The reader will notice that responses to the same XML request message may vary based on the functionality of each CRS. An example of this is the structure of the Availability response, which, although schematically correct, may differ slightly for some hotel chains.
The document’s primary aim is to provide example transactions, and also demonstrate certain differences in responses between one hotel chain and another. It is by no means an exhaustive list of fields that can be returned by each CRS, as this may vary based on the rate, room, type of rate, booking conditions, etc. The developer is asked to consult and code based on the published RateGain XML UltraDirect Transactions document.
### Property Download Site
The Property Download Site (PDS) is accessed via the RateGain Portal and allows access to the list of properties that are available on the RateGain production database:
* The “Agreed Download HCD prop zip” is updated on the PDS site daily. It can be used to identify all properties currently associated to a brand and the last date the data was updated. (UPDATE\_DATE).
* Agreed Download Brand zip is for the hotel brand codes and indicates the current list of brands available.
* The HCD prop zip contains a .csv file with values in the first two columns (brand and pid) may contain leading 0’s (zeroes). This leading zero is essential in the transaction and MUST be included. Therefore, these two columns should be imported as TEXT in order to preserve the character string.
**Examples:**
brand,pid,prop\_name,address1,city,state,postal,country,create\_date,update\_date
AD,1910,Aparthotel Adagio Toulouse Parthénon,86 allées Jean Jaurès,TOULOUSE,,31000,FR,2011-01-19 00:38:17,2018-11-14 00:01:39
brand,pid,prop\_name,address1,city,state,postal,country,create\_date,update\_date
HY,00909,HYATT REGENCY SAN ANTONIO RIVERWALK,123 Losoya St,SAN ANTONIO,TX,78205,US,2011-07-28 18:15:07,2018-09-29 06:10:07
brand,pid,prop\_name,address1,city,state,postal,country,create\_date,update\_date
000055,1545,Maidens Hotel,7 Sham Nath Marg,Delhi,,110054,IN,1997-02-17 00:00:00,2018-12-13 14:10:45
This document does NOT include the retrieval of property static descriptive information such as images, property facilities, area attractions, etc. If the implementation includes content, the details can be found in a separate document titled RateGain HCD XML Content Retrieval Specification.
---
# 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/ultradirect/ultradirect-transaction-samples-and-usage.md?ask=&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.