> 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/soap-http/soap-envelop.md). # SOAP Envelop The SOAP Envelope encapsulates the entire message structure to be transmitted. It consists of two main components: 1. **Header (Optional in SOAP, but required by RateGain)** 2. **Body (Mandatory)** RateGain Enterprise Connectivity uses a **document-literal format** for its web services. #### SOAP Header The SOAP Header contains metadata essential for message processing, including: * **Username and Password**: Corresponding to an account created on the RateGain Enterprise Connectivity customer portal (). * This account must be enabled for HCD content retrieval requests via web services. * **Action Code** * **Transaction ID** While SOAP allows the Header element to be optional, **RateGain Enterprise Connectivity mandates its inclusion** in every request. Additionally, the following elements are required in the SOAP Header: * **ebXML:MessageHeader**: Contains detailed information about the message. * **wsse:Security**: Ensures message-level security. Clients must reference the associated schema files for these elements to determine the required structure, elements, and attributes. Links to these schema files are available for integration guidance.
* *
The following table illustrates specific values that should be present in these elements. | **Element** | **Attribute** | **/ O / C** | **Usage** | **Description** | | -------------- | --------------------------------------- | ----------- | -------------------- | ----------------------------------------------------------------------------------------- | | MessageHeader |


| R |


|


| |


|

SOAP---

ENV:mustUnderstand

| R |

0

1

|

Indicates “true” or

“false”

| |


| version | R | 2.0 | Indicates the ebXML version | | :From |


| R |


|


| | PartyId |


| R |


| Supplier Name | | To |


| R |


|


| | PartyId |


| R | DHISCO |


| | CPAId |


| R | ODDRetrieveInterface | The destination system | | ConversationId |


| R | *some value* | This value can be used by the client to group a set of transactions into a “conversation” | | Service |


| R | ODDRetrieveInterface | The destination service | |


| type | R | 1.0 | Defines the version of the eb:Service element | | Action |


| R | RETRIEVE |

Defines the action to be performed on the

property

| | MessageData |


| R |


|


| | MessageId |


| R |


| Unique Record ID | | Timestamp |


| R |


|


| | Security |


| R |


| Defines the wsse Security element | | UsernameToken |


| R |


| Defines the UsernameToken element | |


| Username | R | *user name* | The client’s username will be defined by RG Enterprise Connectivity | |


| Password | R | *password* | The client’s password will be defined by RG Enterprise Connectivity |
--- # 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/content/content-retrieve/soap-http/soap-envelop.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.