Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Scopes: signature.
  • Optional scopes: extended.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Create a free developer account: Sign up at https://developers.docusign.com (free developer sandbox). Developer accounts authenticate via https://account-d.docusign.com and use the demo API host https://demo.docusign.net; production uses https://account.docusign.com and your account’s own base host. This connector is configured for production - for sandbox testing, swap the auth URLs to account-d.docusign.com.
  2. Create an app and integration key: In the developer account, open Settings (Admin), then Apps and Keys, and create a new app. Copy the integration key (this is DOCUSIGN_CLIENT_ID), generate a secret key (DOCUSIGN_CLIENT_SECRET), and add your redirect URI ending in /oauth/callback/docusign.
  3. Find your account server and account ID: After connecting, call GET https://account.docusign.com/oauth/userinfo (or account-d.docusign.com for developer accounts) with your access token. The response lists your accounts, each with an account_id (GUID) and a base_uri such as https://na3.docusign.net. On each tool call, pass account_id as accountId and the base_uri host without .docusign.net as accountHostPrefix (e.g. na3, or demo for developer accounts). Keep both values from the same account entry so each account reaches its own host. Admins can also see the API Account ID under Settings, then Apps and Keys.
  4. Verify access: Run the List Envelopes tool with your accountHostPrefix, accountId, and a from_date such as the first day of last month.
  5. Go live for production: Apps built in the developer sandbox must pass DocuSign’s go-live review before they can use production accounts. Until then, keep using the developer environment.

​
Provider notes

  • The eSignature REST base URL is account-specific: https://<accountHostPrefix>.docusign.net/restapi/v2.1/accounts/<accountId>/… - both values come from the same /oauth/userinfo account entry, and tools accept only the host prefix so credentials stay pinned to docusign.net
  • Migrating from earlier versions: the accountServer parameter and the interim DOCUSIGN_ACCOUNT_HOST environment variable are gone. Pass the base_uri host without .docusign.net as the accountHostPrefix parameter on each call.
  • The signature scope covers sending and tracking envelopes; the optional extended scope lets refresh tokens be renewed beyond 30 days
  • List Envelopes requires from_date (or specific envelope IDs); Download Envelope Documents returns raw PDF bytes
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as docusign__get_user_info with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.