ISV FAQ | Docusign | Documentation

Question	Answer
Should I use a Docusign developer (demo) account or a trial account for development and testing?	You should use a Docusign developer account for all your development and testing. You should also provide a way for your customers to connect their Docusign developer accounts to your integration for testing. This includes a configuration in your integration to point to the Docusign developer environment. Trial accounts are limited-use production accounts meant for customers who want to experience the service before signing up. Sign up for a developer account.
Do partners get an account in production?	Docusign provides a free special production partner account to members of the Docusign Partner program that builds General Connectors and go through the Partner Application Review process. These are specific accounts to be used to manage your integration keys. If the integration absolutely cannot use a single integration key for all your customers, your customers’ integration keys can also be managed in this partner account. Note: Digital Referral is an eligibility prerequisite for an integration key management account.
Can a special partner production account be used for testing or demos?	The special partner production account cannot send envelopes and therefore cannot be used for testing or demos. Docusign does not recommend testing in production. However, if you would like to test your application in production, you can purchase API plans that enable you to do so.
What is an integration key?	An integration key is a unique identifier for each Docusign integration. It is used with an OAuth authentication flow to obtain an access token. All API calls require an access token. The Docusign integration key correlates to the OAuth client ID. Visit the Key eSignature design options page page to learn about important concepts associated with Integration key management for ISVs. To use your application in production, you must complete the go-live process for your integration key.
How do I obtain an integration key?	Use your developer account’s admin tool (demo.docusign.net) to create an integration key (see Configure your app). To use your application in production, you must complete the go-live process for your integration key.
Do I need to generate a new integration key for each Docusign customer account?	No. Every production integration key is automatically enabled for all users, on all accounts, worldwide.
Do I need to generate a new integration key for each of my customers?	Maybe; it depends on your product’s architecture (see Key eSignature design options).
Do Docusign developer (demo) and production environments use different integration keys?	Yes. You first create your new integration key in the developer (demo) environment. After completing the go-live process, a new integration key (with the same key value) will be created in the worldwide production environment. While the developer and production keys do have the same key value, they are two separate keys and have separate configurations: The developer key’s settings are managed by your developer account. The production key’s settings are managed by the production account selected during the go-live process. Recommendation: set the production key to be managed by your free partner account. After go-live, the two integration keys can be used simultaneously, as they are separate from each other. Continue to use the developer (demo) version for ongoing testing and development.
I have multiple apps that integrate with Docusign. Can I use the same integration key?	No. Each application should have its own integration key. Different versions of an application should use the same integration key.
Is it okay to give my integration key to my customers or others?	No. If, due to your application’s architecture, each of your customers needs their own integration key for your application, then you should create these integration keys for each of your customers. In this case, you’d provide the integration key and its secret or private key to your customers for use with your application. See Key eSignature design options for details.
Which base URI (na2.docusign.net, eu.docusign.net, etc) does my production application use?	Your application should use the oauth/userinfo call to determine the base URI for the user’s account. The `oauth/userinfo` call should be called infrequently, typically when the user logs in or when the application is rebooted. Your integration can also provide a way to have the connecting customer enter their Docusign account ID along with the associated base URI.
How can I view the API logs for troubleshooting?	Use the Docusign API Request logging feature to capture API requests and responses when troubleshooting issues.