DocuSign
Connect DocuSign to send documents for signature, track envelope status, and manage recipients, templates, and bulk sends.
You paste your Docusign app's Integration Key (Client ID) and a generated Secret Key (Client Secret) into PopMCP, plus "demo" in the Environment box if the key was made in the developer sandbox.
App review before this connector works
Docusign must approve your integration key for production through the Go-Live process in Apps & Keys before it can touch a real Docusign account.
- Typical wait
- Instant for integrations that pass the built-in validation; Docusign states that submissions flagged for manual review are 'typically completed within 48 hours or less'
- Cost
- Free to apply, but the production account must be on a plan that includes API access for the integration type you pick; embedded integrations need a special licence arranged with Docusign sales
- Blocked until approved
- Nothing against production. Until go-live, the integration key authenticates only against the demo environment (account-d.docusign.net / demo.docusign.net); calls to the production base path (account.docusign.net / na*.docusign.net) fail, so no real, legally binding envelopes can be sent.
- Works meanwhile
- Everything else. A free Docusign developer account gives instant credentials and a full demo environment - OAuth Authorization Code Grant, JWT, envelopes, templates, webhooks - all working end to end against demo. The 20-API-call prerequisite was removed in the 2025 streamlined go-live, so you no longer have to farm calls first.
Where to apply: Docusign Developer Console > Apps and Keys > select the integration key > Start Go-Live: choose the integration type (private custom / third-party integration key / public / embedded), then enter the production account's admin email, account ID and API account ID. Built-in validation approves eligible integrations on the spot.
- Pick the integration type carefully - once the request is in review or live, the type cannot be changed and Docusign does not support cancelling to switch.
- Embedded signing/sending integrations require a special licence and route you to the sales team rather than instant approval.
- Public integrations (distributed to other Docusign customers) require Docusign Partner Program membership.
- The most common instant-fail is a production account whose plan lacks the API entitlement for the chosen type - eligibility validates against the plan, and the fix is a sales conversation, not a resubmission.
- Go-live copies the integration key into production rather than moving it, so the same key keeps working in demo - but demo and production have separate base paths and separate user/account IDs.
- You must have admin rights on the production Docusign account you are promoting into; a developer account alone is not enough.
- Setup time
- 8 min
- Auth
- OAuth authorization
- API base URL
- https://demo.docusign.net/restapi for developer accounts. For production, the per-account base URI returned by /oauth/userinfo, for example https://na4.docusign.net/restapi
- Rate limits
- Docusign caps eSignature REST API traffic at 1,000 calls per hour per integration key and user, resetting on the hour. Over the cap you get HTTP 429.
Before you begin
- Docusign eSignature account. A free developer account at developers.docusign.com works for testing.
- Account Administrator permissions. Apps and Keys is hidden from non-admin users.
- For a production account, an integration key that has passed Docusign's Go-Live promotion if it was originally created in the demo environment
Get your credentials
Open Apps and Keys
Sign in as an account administrator and go to Settings → Integrations → Apps and Keys. Production accounts use admin.docusign.com/apps-and-keys and developer accounts use admindemo.docusign.com/apps-and-keys.
Apps and Keys
API information and integration keys for this account.
- API Account ID
- 9c2e****-****-****-****-********71ab
- User ID (GUID)
- 3f81****-****-****-****-********02de
- Account Base URI
- https://na4.docusign.net
| App name | Integration Key | Authentication | Created | |
|---|---|---|---|---|
| Internal reportingWeb app | 1a2b3c4d-****-****-****-9f0e1d2c3b4a | Authorization Code Grant | Mar 4, 2026 | ACTIONS |
The Apps and Integration Keys list shows every app on this Docusign account, each with its own ACTIONS menu.
Create an app for PopMCP
Click ADD APP AND INTEGRATION KEY, enter PopMCP as the App Name, then click ADD.
Apps and Keys
Copy the Integration Key
Find the PopMCP row, open its ACTIONS menu and choose EDIT. In General Info, click the copy icon next to Integration Key and paste that GUID into PopMCP's Integration Key (Client ID) field.
PopMCP
Configure authentication and redirect URIs for this app.
The Integration Key is the OAuth client ID. Copy it rather than retyping it.
Answer Yes to storing a secret, then add a secret key
In the Authentication section, under User Application, answer Yes to "Is your application able to securely store a client secret?". Click ADD SECRET KEY, copy the generated value into PopMCP's Secret Key (Client Secret) field, then click SAVE.
PopMCP
| Secret Key | Status | Created |
|---|---|---|
| b7c9****-****-****-****-********e11d | Active | Mar 4, 2026 |
User Application: is your application able to securely store a client secret?
Register PopMCP's redirect URI
Scroll to Additional settings and click ADD URI under Redirect URIs. Paste the callback URL exactly as PopMCP prints it, then click SAVE.
Fill in the Environment box in PopMCP
Leave Environment blank for a live Docusign account. Type demo only if the Integration Key came from a developer account.
Connect in PopMCP
Open your workspace, choose DocuSign in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Auth typepreset | Create an app under Settings → Apps and Keys (or the developer dashboard). The OAuth flow keeps your DocuSign login on DocuSign's side. |
| Integration Key (Client ID)text | Your app's "Integration Key" from Apps and Keys. |
| Secret Key (Client Secret)secret | Generate a "Secret Key" on your app (Authentication → confidential). Stored encrypted; used server-side only and never shown again.Encrypted with AES-256-GCM on save and never shown again. |
| Environmenttext | Leave blank for a live DocuSign account (Production). Enter "demo" only if your Integration Key was created in the DocuSign developer (demo) environment. |
https://app.popmcp.com/api/providers/docusign/callbackAdd this exact URL to your DocuSign app's "Additional settings → Redirect URIs" (Apps and Keys). It must match exactly, or DocuSign rejects the authorization.
PopMCP verifies the credential against DocuSign immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Permissions PopMCP requests
These are the scopes sent to DocuSign at authorization time.
| Scope | Why PopMCP asks for it |
|---|---|
| signature | Lets PopMCP create and send envelopes, read envelope and recipient status, and use templates on behalf of the signed-in user. |
| extended | Returns a refresh token so the connection keeps working after the 8-hour access token expires, instead of asking you to reconnect. |
Verify it worked
The Docusign connector in PopMCP flips to Connected and shows the Docusign account name and account ID it bound to. Asking for your recent envelopes returns real envelope IDs and statuses.
Troubleshooting
invalid_client on connect
Why: The Integration Key and Secret Key are from different environments, or the secret was truncated when copied. Keys are not shared between demo and production.
Fix: Confirm the Environment field matches where the key was created (blank for production, demo for developer), then generate a fresh Secret Key and paste it again.
The redirect URI is not registered for the client_id
Why: PopMCP's callback URL is missing from the app's Redirect URIs list, or differs in case, protocol or trailing slash.
Fix: Copy the callback exactly as PopMCP prints it into Additional settings, Redirect URIs, and save.
consent_required
Why: The Docusign user has not granted the signature and extended scopes to this integration key, or an admin has locked down individual consent.
Fix: Re-run the connect flow and accept the consent screen. On locked-down accounts, ask an admin to grant admin consent for the integration key.
Works in demo but 401s in production
Why: The integration key was created in the developer environment and never promoted.
Fix: Run Docusign's Go-Live process to promote the key to production, or create a new key directly in the production account and leave Environment blank.