Wondering what’s next for npm?Check out our public roadmap! »

docusign-esignDefinitelyTyped icon, indicating that this package has TypeScript declarations provided by the separate @types/docusign-esign package

5.8.1 • Public • Published

The Official DocuSign Node Client

NPM version NPM downloads Build status Coverage Status

NPM module that wraps the DocuSign API

Documentation about the DocuSign API

Documentation about this package

Requirements

Compatibility

  • Node 4+

Note:

This open-source SDK is provided for cases where you would like to make additional changes that the SDK does not provide out-of-the-box. If you simply want to use the SDK with any of the examples shown in the Developer Center, follow the installation instructions below.

Installation

NPM:

  1. Open your preferred command-line console, then navigate to your project.
  2. In the console, type the following commands:
    npm install docusign-esign -save

Dependencies

This client has the following external dependencies:

Minimum:

  • DocuSign-eSign
  • Superagent 3.8.2

Optional:

  • Async v2.6.2
  • Jsonwebtoken v8.2.0
  • Passport-oauth2
  • Path

Code Examples

Launchers

DocuSign provides a sample application code referred to as a Launcher. The Launcher contains a set of 31 common use cases and associated source files. These examples use either DocuSign's Authorization Code Grant or JSON Web Tokens (JWT) flows.

Proof-of-concept applications

If your goal is to create a proof-of-concept application, DocuSign provides a set of Quick Start examples. The Quick Startexamples are meant to be used with DocuSign's OAuth Token Generator, which will allow you to generate tokens for the Demo/Sandbox environment only. These tokens last for eight hours and will enable you to build your proof-of-concept application without the need to fully implement an OAuth solution.

OAuth Implementations

For details regarding which type of OAuth grant will work best for your DocuSign integration, see the REST API Authentication Overview guide located on the DocuSign Developer Center.

For security purposes, DocuSign recommends using the Authorization Code Grant flow.

There are other use-case scenarios, such as single-page applications (SPA) that use Cross-Origin Resource Sharing (CORS), or where there may not be a user to interact with your Service Account. For these use cases, DocuSign also supports JWT and Implicit grants. For Ccode eExamples, see the links below:

Support

Log issues against this client through GitHub. We also have an active developer community on Stack Overflow.

License

The DocuSign Node Client is licensed under the MIT License.

Additional Resources

Install

npm i docusign-esign

DownloadsWeekly Downloads

14,350

Version

5.8.1

License

MIT

Unpacked Size

5.15 MB

Total Files

544

Last publish

Collaborators

  • avatar