Secrets, RSA key pairs and redirect URIs do not carry over at Go-Live; recreate them in production. [2]
Guides · productivity · Popular APIs
Docusign developer account, integration key and Go-Live
Build in a free developer (demo) account with an integration key, then promote the key to a paid production account via Go-Live; production needs new secrets/RSA keys, redirect URIs and the account's base URI.
Researched · not yet run liveLast researched 25 October 2026 · Docusign · provider site
Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Who owns what
A free developer (demo) account owns the integration key; a paid production account becomes its management account at Go-Live.
- Docusign developer account (demo) developer
- Docusign production account (paid) billingYou need admin access on it; the required plan tier is not confirmed [to verify].
Steps
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Create a free developer account
Sign up for a Docusign developer (demo) account on the developer site.
Where: https://developers.docusign.com/
Add an app and integration key
In the developer account's Apps and Keys page add an app; note the integration key, add a secret key (Authorization Code Grant) or generate an RSA key pair (JWT Grant), and redirect URIs.
verapli captures
DOCUSIGN_CLIENT_SECREThere by plain code: encrypted in your browser, never shown to AI.Where: https://admindemo.docusign.com/
Build and test against the demo environment
Make your API calls against demo; Go-Live status and API logs show only when logged into the account that owns the key.
Start Go-Live and pick the production account
From Apps and Keys start Go-Live, choose the integration classification (affects billing) and the paid production account you administer. Eligible keys auto-promote; others show Verification required or Pending approval.
If something goes wrong (1)
- Promotion declined with "Verification required": Complete the one-time identity verification for the production account, then retry from Apps and Keys. [1]
Recreate secrets and switch endpoints
In the production account add new secrets / RSA keys and redirect URIs, use account.docusign.com for OAuth and the base URI returned by UserInfo for API calls; migrate templates and Connect profiles.
Terms and gotchas
Plain-English summary, not legal advice. Each card links its source.
The integration classification chosen at Go-Live affects how envelopes are billed on the production account. [1]
What you end up with
| Env var | Secret | Format | What it is |
|---|---|---|---|
DOCUSIGN_INTEGRATION_KEY | not secret | GUID | Integration key (client ID); GUID kept across Go-Live |
DOCUSIGN_CLIENT_SECRET | secret | GUID-shaped secret | Secret key for Authorization Code Grant (environment-specific) |
DOCUSIGN_USER_ID | not secret | GUID | API user ID (needed for JWT Grant impersonation) [to verify] |
DOCUSIGN_ACCOUNT_ID | not secret | GUID | API account ID |
DOCUSIGN_BASE_URI | not secret | https://{region}.docusign.net | Account base URI from the UserInfo endpoint (differs from demo) |
DOCUSIGN_RSA_PRIVATE_KEY | secret | PEM text block | RSA private key for JWT Grant (environment-specific) |
Pricing
- Free tier: Developer (demo) account is free [to verify].
- Go-Live requires a paid production account; plan tier requirement not confirmed [to verify].
Source [1]
For agents
The same entry as JSON: /api/v1/entries/docusign/developer-and-go-live · requirements /api/v1/requirements/docusign/developer-and-go-live · terms /api/v1/terms/docusign/developer-and-go-live.
Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Docusign developer account, integration key and Go-Live, and how long will it take?"
→ tools/call requirements { "provider_id": "docusign/developer-and-go-live" }Sources
- Go-Live Go-Live promotes the integration key from the developer account to a paid production account; needs OAuth 2.0 configured and admin access on the production account; integration classification affects envelope billing; auto-promotion or "Verification required" one-time identity verification; some integrations go to Pending approval for Docusign review. (Page is script-rendered; read via official search summary [to verify].) · accessed 25 October 2026 · official
- After Go-Live Key keeps its GUID but is duplicated; secrets, RSA key pairs and redirect URIs must be recreated in production; use account.docusign.com for auth and the account base URI from UserInfo; migrate users, templates and Connect profiles. (Read via official search summary [to verify].) · accessed 25 October 2026 · official
- Configure your app Apps and Keys page holds integration keys, secrets, RSA key pairs and redirect URIs [to verify detail; page is script-rendered]. · accessed 25 October 2026 · official
- Docusign Developer FAQ - Integration Keys and Go Live Go-Live status and API logs show correctly only when logged into the account that owns the key. (Read via search summary [to verify].) · accessed 25 October 2026 · official
Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Docusign is not affiliated with verapli.