> 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/xml-ultradirect-specifications/overview/transaction-list.md). # Transaction list The following list provides a brief summary of each of the forms elements that may be submitted. Additional information about these forms may be located in each of the appendices. | **Transaction** | **Description** | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AmenityInformation | This form is designed to allow a BSP to request a list of amenity codes and descriptions. | | BrandInformation | This form is designed to allow a BSP to request all available information about a list of brands identified by brand code. | | PointOfInterestSearch | This form is designed to allow a BSP to obtain a list of Points Of Interest that match a given set of criteria and then base a PropertySearch on a selected Point of Interest. | | PropertySearch | This form is designed to allow a BSP to obtain a list of properties that match a given set of criteria. It can also be used to check the availability status and return a rate range for each matching property for particular dates of stay. | | MultiAvailability | This form is designed to allow a BSP to check the availability status and return a rate range for a set of properties (identified by their property code) for particular dates of stay. | | PropertyInformation | This form is designed to allow a BSP to obtain a variety of information about a property, both from the HCD database and/or the property’s CRS. The DataSet attribute of the PropertyInformation element is used to request data from the HCD database that represents largely static property data such as area attractions, phone, email, restaurants, and such. All other functionality, such as rates and availability are represented in child elements and the request is passed to the actual property for processing. | | BookReservation | This form is designed to allow a BSP to make a reservation at a specific property under specific terms. | | ModifyReservation | This for is designed to allow a BSP to change an existing reservations without having to cancel and rebook. | | CancelReservation | This form is designed to allow a BSP to cancel an existing reservation. | --- # 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/xml-ultradirect-specifications/overview/transaction-list.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.