> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/integrations-and-api-access/integrations-page/as2-integration-setup.md).

# AS2 Integration Setup

This document describes the AS2 connection properties used on the Integrations page and notes on how data exchange is handled.

### AS2 connection properties

1. To connect to the AS2 server, use the autogenerated data and fill in the required data on the recipient side from the integration page `/admin/integrations/list`.
2. Self URL - URL of the DocStudio AS2 server.
3. Self certificate - certificate of the AS2 server.
4. Self ID - self ID of the connection to the AS2 server.
5. Recipient URL - connection URL to the AS2 server. Files will be sent here.
6. Recipient certificate - recipient certificate of the AS2 server.
7. Recipient ID - recipient ID of the connection to the AS2 server.
8. Recipient email - an optional recipient email parameter.
9. Encryption algorithm - an optional encryption parameter. By default, `3des` is used.
10. Signing algorithm - an optional signing parameter. By default, `md5` is used.

{% hint style="info" %}
The client can use different data exchange formats on the AS2 server, and this is defined by the AS2 server configuration. DocStudio does not know the specific folder on the AS2 server where the data should be placed.
{% endhint %}


---

# 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://support.docstudio.com/admin-panel/integrations-and-api-access/integrations-page/as2-integration-setup.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.