> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Node.js SDK

> See how the Node SDK makes using Docusign APIs easier.

## Node.js SDK

The Node.js eSignature SDK is provided by Docusign to help Node.js developers use the
[Docusign eSignature REST API](/docs/esign-rest-api). It is provided as both an
[npm package](https://www.npmjs.com/package/docusign-esign) and an
[open source repo on GitHub](https://github.com/docusign/docusign-esign-node-client). The Node.js eSignature SDK is also used when developers opt to get started with the Node.js
[Quickstart](/docs/esign-rest-api/quickstart), which generates ready-to-use, personalized Node.js code.

## Places to start

[Setup and configuration](/docs/esign-rest-api/sdks/node/setup-and-configuration)

[Authentication](/docs/esign-rest-api/sdks/node/auth)

[SDK reference](https://docusign.github.io/docusign-esign-node-client)

## Compatibility

* The Node.js eSignature SDK is compatible with Node.js 9 and later.
* The Node.js eSignature SDK package is dependent on other Node.js packages. The list of dependencies can be found on the
  [docusign-esign npm registry](https://www.npmjs.com/package/docusign-esign) page. Next to each dependency is the minimum version required for that package.

## SDK versions

New versions of the SDK are released periodically to use the latest version of the eSignature REST API. SDK versions use the standard period-separated
[semantic versioning](https://docs.npmjs.com/about-semantic-versioning) scheme. General release versions are of the form x.y.z, and release candidate (prerelease) versions are of the form x.y.z-rc.

The
[SDK’s changelog](https://github.com/docusign/docusign-esign-node-client/blob/master/CHANGELOG.md) lists each SDK update and its notable changes from the prior version.

Developers are not required to update their applications to new versions of the SDK, unless there’s a specific reason to do so:

* Access to a new eSignature API feature or method.
* An SDK bug fix including security-related issues.
* To support an updated version of one of the SDK's dependencies.

## SDK Issues

If you find any issues with the SDKs, you can open an issue on the
[GitHub repo](https://github.com/docusign/docusign-esign-node-client/issues), or reach out to
[Support](https://support.docusign.com/).