> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Docusign Go-Live > Learn about how to move your integration from the development environment to a production environment, including the requirements for going-live, best practices, and troubleshooting. When you are ready to launch your app in production, you must promote your application’s integration key (IK) from your developer account to a production Docusign account. ## How to Go-Live When you Go-Live, your integration key is copied to the production environment, rather than moved. This means you can continue using the same integration key in the demo environment and in production. Configuration settings such as secrets and redirect URIs are not copied automatically. After promotion, you must configure these values separately in the production environment. Each Docusign API can have different Go-Live requirements, but before starting the Go-Live process, check the following: * Production account requirements * You have a paid production account to manage the integration in production. * ISV partners may qualify for a free management account through the partner program * You have administrator access or [developer access](/platform/create-ik-developer-console#assign-developer-roles) to the production account. * The account has access to each API used by the application. * Integration requirements * Meets all applicable [API resource limits](/platform/resource-limits) * Uses [OAuth 2.0 authentication](/platform/auth) * Uses the correct integration classification ### Go-Live with the Developer Console > **Note** > > This feature is currently in open beta. For more information on access and migration logic, see [Migration and availability](/platform/monitor-your-integration/integration-dashboard#migration-and-availability). The Go-Live process is now integrated into the [Developer Console](/extension-apps/developer-console-overview) experience. From within the console, you can now create integration apps to get demo client IDs and secrets for development and testing, and then take integrations live with a single click. To submit your app to Go-Live, open the Developer Console, select your app, and navigate to the Go-Live or promotion workflow associated with the integration key. See [How to create an IK and manage guest developers](/platform/create-ik-developer-console) for step-by-step instructions. ### Legacy Go-Live process The following sections describe the legacy Go-Live process used prior to the Developer Console experience. These steps are relevant to existing integrations created or promoted through the [legacy Apps and Keys](/tools/api-dashboard) experience. #### Choose an integration classification Your integration classification is determined by your business model and affects both the Go-Live process and production billing behavior. Choose the option that best matches your integration: | Use case | Classification | | ----------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- | | Your integration will be used internally by your employees or your customers’ employees. | Private custom integration | | You are using a partner integration that requires your own integration key. | Third-party integration key | | You are building a public integration that multiple Docusign customers will authorize and use with their own Docusign accounts. | Public integration | | You are embedding Docusign capabilities directly into your own product and offering them to your customers through your Docusign account. | Embedded integration | ##### Public integration requirements To launch a public integration, you must join the [Docusign Partner Program](https://partners.docusign.com/s/). ##### Embedded integration requirements Embedded integrations require ISV Embed partner licensing. ## Go-Live status Your app’s Go-Live status may display one of the following values: | Status | Description | | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Not started | Your app has been created, but an integration type has not been selected. The Go-Live process cannot be started until an integration type has been selected. | | Ready to submit | The Go-Live process can be started. | | Pending approval | Your app is being reviewed against Go-Live requirements. | | Declined | The integration requires additional manual review or information before promotion can continue. Manual reviews are typically completed within 24–48 hours. If a **Verification required** link is displayed along with this status, your app qualifies for automatic promotion to prod after a one-time identity verification process is completed. See [Automatic promotion](/docs/esign-rest-api/go-live#automatic-promotion) for details. | | App is live | The integration has been successfully promoted to the selected production account. | ## Troubleshooting and support If your integration does not meet the required criteria, you will be prompted to update the application before resubmitting. For additional guidance: * See [Go-Live troubleshooting](/platform/go-live/troubleshooting) for common review failures. * See [After Go-Live](/platform/go-live/after-go-live) for required production configuration changes. Contact [Docusign Support](https://support.docusign.com/s/contactSupport) if you have a paid support plan or are enrolled in the [Docusign Partner Program](https://partners.docusign.com/s/). ## Next steps Review the Go-Live requirements for the APIs used by your integration: * [eSignature REST API](/docs/esign-rest-api/go-live) * [Agreement Manager API](/docs/agreement-manager-api/go-live) * [Workflow Builder API](/docs/workflow-builder-api/publishing-go-live) * [Workspaces API](/docs/workspaces-api/go-live) * [Connected Fields API](/docs/connected-fields-api/go-live) * [CLM API](/docs/clm-api/go-live) * [Admin API](/docs/admin-api/go-live) * [Click API](/docs/click-api/go-live) * [ID Evidence API](/docs/idevidence-api/go-live) * [Monitor API](/docs/monitor-api/go-live) * [Notary API](/docs/notary-api/go-live) * [Rooms API](/docs/rooms-api/go-live) * [Web Forms API](/docs/web-forms-api/go-live) > Learn about how to move your integration from the development environment to a production environment, including the requirements for going-live, best practices, and troubleshooting. ## Docs - [After Go-Live](https://developers.docusign.com/platform/go-live/after-go-live.md): See best practices for configuring your integration after it goes live. - [Go-Live troubleshooting](https://developers.docusign.com/platform/go-live/troubleshooting.md): Get help with some of the common problems experienced by integrations failing the go-live review.