> 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 # Go-Live > Learn how to push your integration from the developer account into production, the requirements you need to meet, and about best practices for configuring your integration once it goes live. ## Go-Live When you are ready to launch your app in a production environment, you will need to promote your [integration key](/platform/configure-app#integration-key) from your developer account to a production Docusign account. This will enable: * Sending of legally binding eSignature requests. * Any user on any production Docusign account to access your app. ![The Go-Live process](/_fern-files/_img/4559f5d420879d971a535930c265a013d68d339cbb48b3ae23ed23658c556af1.webp) ## Go-Live prerequisites Before starting the Go-Live process, make sure that you have: * [OAuth 2.0 authentication](/platform/auth) configured for your app. * A paid production account that will serve as the management account for the app in the production environment. ISV partners can apply for a free IK management account via the partner program. * Administrator access or [developer access](/platform/create-ik-developer-console#assign-developer-roles) to the production account. ## Promoting your app To promote your app, you must: 1. Choose a classification for your app. Your app’s classification is determined by its business model. Choose the option that aligns with your role and the type of app that you are building. Your choice of **integration classification** at Go-Live also affects how envelopes are billed on your production account. Each classification uses a different billing model for envelope sends. To understand the specific pricing for each send type, review your Docusign production plan details or contact your Docusign representative. The options and their associated requirements are listed below: | Use case | Classification to choose | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- | | Your integration will be directly used by your employees or your customers’ employees. | Private custom integration | | You want to use a Docusign partner integration for your business needs, and that integration requires you to provide your own integration key (IK). | Third-party integration key | | You’re building a public integration for multiple Docusign customers, who will access it using their own Docusign accounts. They will authorize your integration to connect with their account directly. As they use your integration, you’ll earn referral revenue from Docusign based on their usage. **Note**: You’ll need to join the Docusign Partner Program to launch a public integration. | Public integration | | You’re embedding one or more Docusign features into your own product and offering them as a service to your customers. Your customers won’t need their own Docusign accounts to access this. Instead, they’ll use the features through your Docusign account, which you own and control. **Note**: To use this model, you’ll need to be an ISV Embed partner, which requires a special license. | Embedded integration | 2. Start the Go-Live process in eSignature Admin. #### See how to start the Go-Live process 1. Open the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) page in your developer account. 2. Next to the integration key you want to promote, select **Actions > Select Go-Live account**. 3. Log in and select your production account to use. You must be an administrator or have [developer access](/platform/create-ik-developer-console#assign-developer-roles) on the production account that you select. Each integration key in the production environment must belong to a paid or partner production Docusign account. You can choose an account with a different email address than the one associated with your developer account, if needed. The integration key will be tied to that account for management purposes, but after promotion, the key can be used to make API calls against any account. After you select a production account, the next steps depend on whether your integration qualifies for automatic promotion to production or whether a Go-Live review is required. See the next sections for details. ### Automatic promotion Your integration may be eligible for automatic promotion to production without a Docusign review. If you select a production account to promote to and your integration can be promoted automatically, you'll see one of the following statuses after you log in to the production account: * **App is live** with a **View in production** link. * **Declined** with a **Verification required** link. This means that a one-time identity verification process must be completed for the production account. See [Verify Your Account Administrator Identity to Unlock Account Features](https://support.docusign.com/s/document-item?bundleId=pik1583277475390\&topicId=task-6561.html) for steps. Afterward, you can return to the Apps and Keys page and select **Actions>Select Go-Live account** to initiate automatic promotion. Going forward, all eligible integrations will follow the automatic promotion flow for this production account. ### Go-Live review If you select a production account to promote to and your integration requires Docusign review, the status changes to **Pending approval**. After the app has passed review, you will receive an email notification and the key’s status changes to **App is live**. If your app fails the review, its status changes to **Declined**. See [Go-Live troubleshooting](/platform/go-live/troubleshooting) for guidance. ## After your app is live When your app reaches live status, the key is enabled in the production environment and is displayed in the production account into which it has been promoted. When your app is promoted into the production environment, its integration key is duplicated into the production environment rather than moved. The integration key's configuration parameters such as secrets and redirect URIs are not also duplicated; you must add them in the production environment to match the settings for your app in the developer environment. See [After Go-Live](/platform/go-live/after-go-live) for details. ## API endpoints The developer and production endpoints for most Docusign APIs use slightly different paths. This table lists the endpoint base paths for each Docusign environment so you know how to modify your code when you migrate from the developer environment to production. | Environment | API base URI | Web site login URL | | ----------- | --------------------------------------------- | ------------------ | | Developer | `https://demo.docusign.net/restapi/v2.1/` | | | Production | `https://{server}.docusign.net/restapi/v2.1/` | | For information on the CLM API endpoints, see CLM [API 101](/docs/clm-api/clm101). **Note:** \{server} is the data center location of your production account (for example, **CA**, **NA2**, or **EU**). You can obtain your production data center location from: * The `base_uri` in the response of a call to the [/oauth/userinfo](/platform/auth/reference/user-info). If you obtain the `base_uri` in this way, you should do it once when the user authenticates for the first time and cache the response. * The **Account Base URI** section of the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) page. For a full list of sites, see [Site certificates](https://support.docusign.com/s/document-item?bundleId=khf1655309726546\&topicId=kkh1657307586557.html&_LANG=enus). To access production API endpoints, you'll need to enable your integration key in the production environment. ## Next steps * For a list of issues that can prevent an app from passing a Go-Live review, see [Go-Live troubleshooting](/platform/go-live/troubleshooting). * For a list of configuration changes required for the production environment, see [After Go-Live](/platform/go-live/after-go-live).