> 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/content/content-retrieve.md).

# Content Retrieve

## Overview

### Technology Overview <a href="#id-overview.-technologyoverview" id="id-overview.-technologyoverview"></a>

The RateGain HCD (Hotel Content Database) Content Retrieval Interface is a JAX-WS Document-Literal web service that leverages SOAP over HTTP/HTTPS, using OTA XML 2005B as the message payload format.

### Open Travel Alliance <a href="#id-overview.-opentravelalliance" id="id-overview.-opentravelalliance"></a>

The Open Travel Alliance (OTA) is a standards body comprising industry leaders from various travel sectors. Its primary goal is to develop and maintain standardized XML message structures to facilitate seamless data exchange among travel companies. RateGain Enterprise Connectivity has adopted the OTA 2005B message structure and codes for its HCD (Hotel Content Database) Content Retrieval Interface.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.rategain.com/content/content-retrieve.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.