PLEASE! Share your feedback in a two-question survey.
GitHub repo: code-examples-node
This GitHub repo includes code examples for the Web Forms API, Maestro API, Docusign Admin API, Click API, eSignature REST API, Monitor API, and Rooms API.
This repo is a Node.js application that supports the following authentication workflows:
Authentication with Docusign via Authorization Code Grant. When the token expires, the user is asked to re-authenticate. The refresh token is not used.
Authentication with Docusign via JSON Web Token (JWT) Grant. When the token expires, it updates automatically.
For more information about the scopes used for obtaining authorization to use the eSignature API, see Required scopes.
For a list of code examples that use the eSignature API, see the How-to guides overview on the Docusign Developer Center.
Note: To use the Rooms API, you must also create your Rooms developer account. Examples 4 and 6 require that you have the Docusign Forms feature enabled in your Rooms for Real Estate account.
For more information about the scopes used for obtaining authorization to use the Rooms API, see Required scopes.
For a list of code examples that use the Rooms API, see the How-to guides overview on the Docusign Developer Center.
For more information about the scopes used for obtaining authorization to use the Click API, see Required scopes
For a list of code examples that use the Click API, see the How-to guides overview on the Docusign Developer Center.
Note: To use the Monitor API, you must also enable Docusign Monitor for your organization.
For information about the scopes used for obtaining authorization to use the Monitor API, see the scopes section.
For a list of code examples that use the Monitor API, see the How-to guides overview on the Docusign Developer Center.
Note: To use the Admin API, you must create an organization in your Docusign developer account. Also, to run the Docusign CLM code example, CLM must be enabled for your organization.
For information about the scopes used for obtaining authorization to use the Admin API, see the scopes section.
For a list of code examples that use the Admin API, see the How-to guides overview on the Docusign Developer Center.
The Web Forms API is available in all developer accounts, but only in certain production account plans. Contact Docusign Support or your account manager to find out whether the Web Forms API is available for your production account plan.
For more information about the scopes used for obtaining authorization to use the Rooms API, see Required scopes.
For a list of code examples that use the Web Forms API, see the How-to guides overview on the Docusign Developer Center.
Note: If you downloaded this code using Quickstart from the Docusign Developer Center, skip items 1 and 2 as they were automatically performed for you.
A free Docusign developer account; create one if you don't already have one.
A Docusign app and integration key that is configured to use either Authorization Code Grant or JWT Grant authentication.
This video demonstrates how to obtain an integration key.
To use Authorization Code Grant, you will need an integration key and a secret key. See Installation steps for details.
To use JWT Grant, you will need an integration key, an RSA key pair, and the User ID GUID of the impersonated user. See Installation steps for JWT Grant authentication for details.
For both authentication flows:
If you use this launcher on your own workstation, the integration key must include redirect a URI of http://localhost:3000/ds/callback
If you host this launcher on a remote web server, set your redirect URI as
{base_url}/ds/callback
where {base_url} is the URL for the web app.
Note: If you downloaded this code using Quickstart from the Docusign Developer Center, skip step 4 as it was automatically performed for you.
cd <Quickstart folder>
or cd code-examples-node
npm install
dsClientId
.dsClientSecret
.signerEmail
and a name as signerName
.
Note: Protect your personal information. Please make sure that appsettings.json will not be stored in your source code repository.npm start
Note: If you downloaded this code using Quickstart from the Docusign Developer Center, skip step 4 as it was automatically performed for you.
Also, in order to select JSON Web Token authentication in the launcher, in config/appsettings.json change the quickstart
setting to "false"
.
cd <Quickstart folder>
or cd code-examples-node
npm install
impersonatedUserGuid
.dsClientId
.signerEmail
and a name as signerName
.
Note: Protect your personal information. Please make sure that appsettings.json will not be stored in your source code repository.npm start
See Docusign Quickstart overview on the Docusign Developer Center for more information on how to run the JWT grant remote signing project and the Authorization Code Grant embedded signing project.
To use the payments code example, create a test payment gateway on the Payments page in your developer account. See Configure a payment gateway for details.
Once you've created a payment gateway, save the Gateway Account ID GUID to appsettings.json.
This repository uses the MIT License. See LICENSE for details.
Pull requests are welcomed. Pull requests will only be considered if their content uses the MIT License.