> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/external-document-storage/integration-interface-specification/ess-get-webservice-method.md).

# ESS Get-Webservice Method

The purpose of this webservice method is to return the document data to the LogicNets system.

### Request

The relative base URL of the web method is as follows:

*/Get?sessionkey=\&reportkey=\&userkey=.*

Method: *GET*

| Property    | Description                                                   | Example     |
| ----------- | ------------------------------------------------------------- | ----------- |
| Session-key | This is the session-key provided by the ESS in the Start-URL. | 12345       |
| Report-key  | This is the report-key provided by the ESS in the Start-URL.  | Document123 |
| User-key    | This is the user-key provided by the ESS in the Start-URL.    | UserA       |

### Response

The ESS must respond to the request with an XML document and HTTP status code.

| Status Code | Status Text           | Description                                                         |
| ----------- | --------------------- | ------------------------------------------------------------------- |
| 200         | Success               | This means the request was successful and the system returned data. |
| 403         | Forbidden             | This means the authentication failed.                               |
| 500         | Internal Server Error | This means there were unexpected server errors.                     |

### **Examples**

| Description                                            | Examples                                         |
| ------------------------------------------------------ | ------------------------------------------------ |
| Response of an empty document                          | *LoadResponse-NewDocument.xml*                   |
| Response of an existing document                       | *LoadResponse-ExistingDocument.xml*              |
| Response of an existing document with user information | *LoadResponse-ExistingDocument-OverrideUser.xml* |

## Attachments

* [LoadResponse-ExistingDocument-OverrideUser.xml.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/m2lkfh-LoadResponse-ExistingDocument-OverrideUser.xml.zip)
* [LoadResponse-ExistingDocument.xml.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/63lkfy-LoadResponse-ExistingDocument.xml.zip)
* [LoadResponse-NewDocument.xml.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/h4lkf3-LoadResponse-NewDocument.xml.zip)


---

# 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://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/external-document-storage/integration-interface-specification/ess-get-webservice-method.md?ask=<question>&goal=<user_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.