> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/signing-up-for-a-subscription/user-plans/for-teams-and-enterprise/envelope-and-api-plans.md).

# Envelope & API Plans

emSigner Envelope and API plans are designed for enterprises and financial institutions that need to execute legally valid eSignatures at scale using UI driven and API based signing

**Includes everything in Professional plus:**

* **Demographic data verification** – Validate user details against trusted sources.
* **Webhooks support** – Enable real-time workflow automation.
* **Cloud storage integration** – Connect with Google Drive and Dropbox.
* **REST API access** – Integrate signing workflows into your applications.
* **Embedded signing** – Allow users to sign documents seamlessly within your app or website by invoking emSigner as an extension.

To get started, visit <https://web.emsigner.com/subscription/TeamsAndEnterprise>


---

# 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://support.emsigner.com/signing-up-for-a-subscription/user-plans/for-teams-and-enterprise/envelope-and-api-plans.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.