# SOAP Body

The SOAP Body contains the message payload and is a mandatory part of the SOAP Envelope. For the HCD Content Retrieval Interface, the payload is an **OTA\_HotelDescriptiveInfoRQ** OTA XML document, which serves as the request structure for retrieving hotel content.

#### Example SOAP Body <a href="#soapbody-examplesoapbody" id="soapbody-examplesoapbody"></a>

The following example SOAP Envelope shows the use of the ebXML Header and wsse Security elements within the SOAP Header.<br>

```xml
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/
" SOAP- ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/
" xmlns:xsd="
http://www.w3.org/2001/XMLSche
 ma" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance
">
                <SOAP-ENV:Header>
                                <ns2:MessageHeader xmlns:ns1="
http://schemas.xmlsoap.org/soap/envelope/
" ns1:mustUnderstand="false" xmlns:ns2="
http://www.oasis-
 
open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
" ns2:version="4.0">
                                                <ns2:From>
                                                                <ns2:PartyId>Customer</ns2:PartyId>
                                                </ns2:From>
                                                <ns2:To>
                                                                <ns2:PartyId>DHISCO</ns2:PartyId>
                                                </ns2:To>
                                                <ns2:CPAId>ODDRetrieveInterface</ns2:CPAId>
                                                <ns2:ConversationId>ConvID</ns2:ConversationId>
                                                <ns2:Service ns2:type="4.0">ODDRetrieveInterface</ns2:Service>
                                                <ns2:Action>RETRIEVE</ns2:Action>
                                                <ns2:MessageData>
                                                                <ns2:MessageId>10141</ns2:MessageId>
                                                                <ns2:Timestamp>2007-09-17T19:50:22.961+00:00</ns2:Timestamp>
                                                </ns2:MessageData>
                                </ns2:MessageHeader>
                                <Security xmlns="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
 wssecurity-secext-1.0.xsd">
                                                <UsernameToken>
                                                                <Username>
customer.name
@
companyname.com
</Username>
                                                                <Password>password</Password>
                                                </UsernameToken>
```


---

# 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/content/content-retrieve/soap-http/soap-body.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.