# DocuSign setup for PopMCP

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.

- Auth: OAuth authorization
- Setup time: 8 min
- 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
- Credentials screen: https://admin.docusign.com/apps-and-keys
- Provider docs: https://developers.docusign.com/platform/auth/authcode/

## Approval required before this 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.

## 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

### 1. 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`.

Screen: https://admin.docusign.com/apps-and-keys

### 2. Create an app for PopMCP

Click ADD APP AND INTEGRATION KEY, enter `PopMCP` as the App Name, then click ADD.

### 3. 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.

### 4. 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.

### 5. 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.

### 6. 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.

## Fields PopMCP asks for

- Auth type (connectionType): 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) (clientId) [required]: Your app's "Integration Key" from Apps and Keys.
- Secret Key (Client Secret) (clientSecret) [required]: Generate a "Secret Key" on your app (Authentication → confidential). Stored encrypted; used server-side only and never shown again.
- Environment (environment): Leave blank for a live DocuSign account (Production). Enter "demo" only if your Integration Key was created in the DocuSign developer (demo) environment.

## Callback URL to register

https://app.popmcp.com/api/providers/docusign/callback

## Scopes requested

- signature
- extended

## Verify

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

Cause: 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

Cause: 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

Cause: 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

Cause: 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.

---

Source: https://www.docs.popmcp.com/docs/integrations/docusign/