> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/docusign.md).

# DocuSign

## OAuth app properties

| Property                | Value                                                                                                                                                                                                                                                                         |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** After go-live the integration key works with any Docusign production account. Before go-live it works only with developer (demo) accounts.                                                                                                                           |
| **Vendor review**       | **Required** for production: the Go-Live review promotes the integration key to a production account. The app must use OAuth 2.0, stay within the API resource limits and have the right integration classification. A public integration needs the Docusign Partner Program. |
| **Review time**         | Some apps are promoted automatically. Manual reviews usually take 24–48 hours.                                                                                                                                                                                                |
| **Users before review** | Developer (demo) accounts only. No production users.                                                                                                                                                                                                                          |
| **App owner**           | A developer account to build the app and a paid Docusign production account (admin or developer access) to own it after go-live. ISV partners may get a free one through the Partner Program.                                                                                 |
| **Regions**             | One integration key for all production data centers. Each account has its own API base URI, which Docusign returns at sign-in.                                                                                                                                                |
| **Client secret**       | No expiry documented. Secrets are not copied at go-live; create a new one in the production account.                                                                                                                                                                          |
| **Rate limits**         | Per Docusign account, shared by all apps: 3,000 requests per hour and 500 per 30 seconds in production (200 per 30 seconds in the developer environment).                                                                                                                     |
| **Checked**             | 2026-11-13                                                                                                                                                                                                                                                                    |

**Limitations**

* The connector requests only the `signature` scope, not `extended`. Docusign then keeps the refresh token's first expiry date, typically 30 days after the user connected, and the user has to connect the account again.
* The connector uses the developer environment (`account-d.docusign.com`) unless `production` is set to `true` in the `appmixer:docusign` configuration. Set it after go-live, together with the production secret.
* Redirect URIs are not copied at go-live either. Add `https://<your-appmixer-api>/auth/docusign/callback` again in the production account.

Sources: [Go-Live](https://developers.docusign.com/platform/go-live/), [eSignature Go-Live](https://developers.docusign.com/docs/esign-rest-api/go-live/), [API resource limits](https://developers.docusign.com/platform/resource-limits), [Authentication scopes](https://developers.docusign.com/platform/auth/reference/scopes/). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Register the app

Go to the [Apps and Keys](https://admindemo.docusign.com/apps-and-keys) page (you can also get there from the [Docs](https://developers.docusign.com/platform/configure-app/))

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-800bbe799ffd59dac220fb1a9b61f68f3b6af5c1%2Fdocusign-1.png?alt=media" alt=""><figcaption></figcaption></figure>

Add a new app:

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-6441474ac163629fb2f62098d3c6395a38e6c4c0%2Fdocusign-2.png?alt=media" alt=""><figcaption></figcaption></figure>

Get the ClientId, ClientSecret and set the redirect URI:

`clientId`: Integration Key

`clientSecret`: Secret Keys

set the Redirect URI to `https://[YOUR_API_BASE]/auth/docusign/callback`, for example <https://api.appmixer.com/auth/docusign/callback>

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-85731e1e481ac9a2150c91c2c51c06c96a1cf085%2Fdocusign-3.png?alt=media" alt=""><figcaption></figcaption></figure>

## Backoffice configuration

Configuration ID: `appmixer:docusign` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Integration key of the Docusign app registered above. Not needed when Docusign is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Secret key of the same app. After go-live, use the secret created in the production account. Not needed with the Auth Hub.
* `production` — Optional. `true` connects to the Docusign production environment (`account.docusign.com`). Without it the connector uses the developer environment (`account-d.docusign.com`). Set it after go-live.

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:docusign -u -d '{
  "clientId": "<integration key>",
  "clientSecret": "<secret key>"
}'
```


---

# 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://docs.appmixer.com/connector-configuration/docusign.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.
