After Go-Live | Docusign

After you’ve completed the Go-Live process and promoted your app into the production environment, you should do a final check to make sure that your app is configured correctly to work there.

To configure it to work in a production environment, make sure that you have:

Defined the OAuth settings for your production environment
Updated your app to use production API endpoints
Migrated your users, templates, and other settings from the development environment to production

Defining OAuth settings for production

The OAuth settings for your production account and developer account are separate. When you Go-Live, a new production version of your integration key (with the same value) is created and associated with your production account. You should configure this account, known as the OAuth Management Account, with the production settings for OAuth.

For Authorization Code Grant and Implicit Grant applications, add redirect URIs and secrets as required by your configuration.
For JSON Web Token (JWT) Grant applications, add RSA key pairs and redirect URIs as needed. Organization administrators can also proactively grant scope permissions to the integration key for their organization’s accounts.

Using production API endpoints

Update your integration to use the production environment endpoints:

Update the hostname for the Authentication Service. Update your OAuth2 authentication host to https://account.docusign.com instead of https://account-d.docusign.com.
Update API calls to use the account’s base URI. You must update your integration to use your account’s base URI for API calls, instead of https://demo.docusign.net. You can use the Authentication Service UserInfo endpoint to get the base URI for an account.

Note: Accounts move between base URIs infrequently, so the data can be cached for a day or more.

Migrating users, templates, Connect profiles, and settings to production

Production account settings and data, including Connect profiles, are separate from your developer account settings and data. When you promote your app into production, you must also migrate your settings, Connect profiles, and data so that it can function correctly.

Add users, templates, Connect profiles, and settings to your production account using Docusign Admin or the eSignature REST API.

Make sure that your production account has the same account settings and options enabled that your application used in your developer account.

Note: Developer accounts may have features that are not available in your production environment without purchasing a higher-tier product. Make sure that you’ve selected the right API Plan for the features you need. If you’re using a different Docusign plan for your application, check with your Docusign business or technical contact.