Repository: eg-01-node-jwt
A screencast for this launcher is available:
This software is an example of a System Integration. This type of application interacts with DocuSign on its own. There is no user interface and no user is present during normal operation.
The application uses the OAuth JWT grant flow to impersonate a user in the account.
This launcher example includes two examples:
- Send an html, Word, and PDF file in an envelope to be signed.
- List the envelopes in the account that are less than 30 days old.
Requirements: Node v8.10 or later
Download or clone this repository. Then:
cd eg-01-node-jwt
npm install
There are two ways to configure the example's settings:
- Edit the
dsConfig.js
file in the root directory of the example. - Set environment variables before running the example.
Your DocuSign Integration Key (clientId) must be configured for a JWT OAuth authentication flow:
-
Create a public/private key pair for the key. Store the private key in a secure location. You can use a file or a key vault.
-
The example requires the private key. Provide it as a string, as configuration setting
privateKey
. -
If you will be using individual permission grants, you must create a
Redirect URI
for the key. Any URL can be used. By default, this example useshttps://www.docusign.com
This redirect url is just used for obtaining consent. You can use the docusign.com default in your test example.For production, DocuSign recommends using Organization administration to proactively grant consent to the client ID, the Integration Key.
The JWT will impersonate a user within your account. The user can be an individual or a user representing a group such as "HR".
Your application will need the guid assigned to the user. The guid value for each user in your account is available from the Administration tool in the Users section.
To see a user's guid, Edit the user's information.
On the Edit User screen, the guid for the user is shown as
the API Username
.
npm start
Submit support questions to StackOverflow. Use tag docusignapi
.
Contributions via Pull Requests are appreciated. All contributions must use the MIT License.
This repository uses the MIT license, see the LICENSE file.