Skip to content
Node.js SDK

eSignature SDK for Node.js applications

Send documents for signature from your Node.js code with the BoldSign Node.js SDK. Signers sign in their browser from an email link, or inside your app.

Create free API sandboxBook a walkthrough
  • Install from npm
  • API key or OAuth 2.0
  • Webhooks for every status change
Your CompanyPreviewSend
Assignee
David
SERVICE AGREEMENT
Company signatureSign here*
Client signatureSign here*
agreements.jsNode.js SDK
const documentApi = new DocumentApi(apiClient);const signer = new DocumentSigner();signer.name = "David";signer.emailAddress = "david@cubeflakes.com";const request = new EmbeddedDocumentRequest();request.title = "Service Agreement";request.signers = [signer];request.sendViewOption =
  EmbeddedDocumentRequest
    .SendViewOptionEnum.PreparePage;request.showToolbar = true;const embeddedSendCreated = await  documentApi.
    createEmbeddedRequestUrlDocument(
      request);const sendUrl = embeddedSendCreated.sendUrl;
Sample Node.js web app at yourapp.example with BoldSign embedded: the prepare page of a service agreement assigned to David, with Preview and Send buttons, beside the Node.js code from BoldSign’s docs that creates this embedded request

Trusted by 100,000+ organizations worldwide

Samsonite
Ryanair
Hyatt
Sony
Crumbl Cookies
Payroc
Cost Plus
The problem

Why is adding eSignatures to a Node.js app harder than it looks?

Signing is quick. Legal validity, identity checks, reminders, an audit trail, and a sealed PDF are not. With the BoldSign Node.js SDK, you get all five from your Node.js code.

  • Drawing a signature is not the job

    A canvas and a submit button take an afternoon. The legal record takes far longer.

  • The finished file has to prove itself

    That means a trusted certificate on the PDF, a timestamp per action, and storage you control.

  • Everything after launch is yours

    Reminders, retries, status tracking, and backups all sit in your own codebase.

The solution

How can you add eSignatures to a Node.js app without building them?

The BoldSign Node.js SDK gives your code two routes to a signature. BoldSign runs the signing behind both. Your app creates the document, names the signers, and tracks what comes back.

  • Send for signature from your code

    Your server passes the document and signers to BoldSign, which emails each signer a private link.

  • Embed signing in your product

    BoldSign returns a signing URL you can frame in your own page. The signer signs the document inside your app, without leaving it.

Capabilities

What can your Node.js app do with the Node.js eSignature SDK?

The BoldSign Node.js SDK handles the whole signing flow inside your app. Every completed PDF is digitally signed.

  • Send documents for signature

    Send a contract or form from Node.js to one signer or several, in the order you set.

    See the eSignature API

  • Sign inside your app

    Serve the signing page from your own Node.js app, so the signer never leaves it.

    See embedded signing

  • Prepare and send in your app

    Your users place the fields and send the document from your own Node.js screens.

    See embedded sending

  • Send from templates

    Keep one template with its fields, then send it to new signers from Node.js.

    See templates

  • Check who is signing

    Set a check for each signer: access code, email code, SMS code, KBA, or ID verification.

    See signer authentication

  • Know when it is signed

    Handle each status change on your webhook route, then download the signed PDF and audit trail.

    See webhooks

Works in: your Node.js server code. Keep the SDK out of browser bundles, since it carries your API key.

Get started

How do you implement electronic signatures in Node.js?

You implement BoldSign eSignatures in Node.js in 3 steps: install the SDK, authenticate, and send.

  1. Install from npm

    npm install boldsign

    Runs on Node.js 12 or later.

  2. API authentication

    const documentApi = new DocumentApi("https://api.boldsign.com");documentApi.setApiKey("Your-API-Key-Here");

    Connect your API key, or use an OAuth 2.0 token.

  3. Send the document

    const sendDocumentResponse = await documentApi.sendDocument(...);

    The response holds the document ID.

Using an AI coding tool? Connect BoldSign’s coding assistant (MCP), then try this prompt. Set up the coding assistant.Write a Node.js function that sends a service agreement for signature through BoldSign.

See the full Node.js walkthrough
Why BoldSign

Why choose BoldSign for Node.js developers

BoldSign suits Node.js teams that want signing in their product without building or maintaining it.

  • Typed from the start

    The SDK ships TypeScript type definitions. Your editor autocompletes BoldSign classes and flags mismatched fields before runtime.

  • Write Node.js code with your AI coding tool

    BoldSign’s coding assistant (MCP) plugs into VS Code, Cursor, or Claude. It answers SDK questions from BoldSign’s docs, with no API key.

  • Build it all before you pay

    Run the whole integration against a free sandbox, then swap in a live key.

  • Signers need no account

    Signers need no BoldSign account and nothing to download.

  • Legally binding signatures

    Signatures you collect with BoldSign are legally binding under the ESIGN Act, UETA, and eIDAS.

Security

How are documents sent from your code kept secure?

BoldSign encrypts every document twice with AES-256. Independent auditors check its security controls against SOC 2 Type 2. Your account lists each standard on its Compliance page, shown below.

Compliance

BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.

US flag

Data Residency

Active (US - Global)

Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.

View Data Residency Policy
HIPAA logo

HIPAA Compliance

Enabled

Enable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.

View Details
PCI DSS logo

PCI DSS

Compliant

Payments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.

View PCI DSS Policy
CCPA logo

CCPA & CPRA

Compliant

Ensures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.

View Privacy Policy
AICPA SOC logo

SOC 2 Type II

Compliant

BoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.

Request SOC 2
US flag

UETA & ESIGN

Compliant

BoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).

View UETA & ESIGN Policy
EU flag

eIDAS (SES)

Compliant

BoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.

View SES Policy
EU flag

eIDAS (QES)

Enabled

Enable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.

View QES Policy
The compliance panel in your BoldSign account.
For IT and procurement

Security and procurement documents for eSignature

IT and procurement teams can read BoldSign’s security policy, data processing agreement, and subprocessor list online. They can also request the SOC 2 Type 2 report.

What it costs

Limits and costs to know before you send from Node.js with BoldSign

The BoldSign Node.js SDK is free to install from npm. Live documents run on a BoldSign API plan. Prices are in USD.

  • $30 Enterprise API plan, per month 40 envelopes included, then $0.75 each.
See all limits and add-on prices
Good to know
  • 2,000 API requests an hour per account The sandbox allows 50 an hour.
Related

More guides for building eSignatures in Node.js

  • Page

    All eSignature SDKs

    Compare the five official BoldSign SDKs.

    See all SDKs
  • Page

    Embedded signing

    Open the signing page inside your own app.

    See embedded signing
  • Code samples

    Node.js code samples

    See send, embedded sign, and template requests as full Node.js examples on GitHub.

    View samples on GitHub
  • Guide

    Build an AI agent

    Let an AI agent send documents through the BoldSign MCP server.

    Read the guide
Common questions

Questions about the Node.js eSignature SDK

Is there a Node.js SDK for eSignatures?

Yes. The BoldSign Node.js SDK, published on npm as boldsign, is BoldSign’s official SDK for Node.js. People sign electronically, and BoldSign seals each completed PDF with an AATL certificate.

Does the Node.js SDK include TypeScript types?

Yes. The package ships its own type definitions. TypeScript editors get autocomplete and type checking on BoldSign classes, with no separate types package to install.

How do webhooks work with the Node.js SDK?

Webhooks are set up once in your BoldSign account, under API then Webhooks, not in the SDK. BoldSign posts each status change to your HTTPS endpoint, so your Node.js app never polls for status. Set up a webhook.

Does the Node.js SDK support OAuth 2.0?

Yes. Pass a bearer token with setDefaultAuthentication instead of an API key. See OAuth 2.0 setup.

How do I use the Europe, Canada, or Australia region?

Pass your region’s base URL to the API class constructor, such as api-eu.boldsign.com for Europe. US accounts need no change. See all base URLs.

Can I test the Node.js SDK for free?

Yes. Create a free BoldSign API sandbox, then use its API key with the Node.js SDK. Sandbox documents are for testing only.

Get started

Send your first document from Node.js

Open a free BoldSign API sandbox, install the Node.js SDK from npm, and send your first document.

Create free API sandboxBook a walkthrough
  • 30-day free trial
  • No credit card required

Last updated: October 18, 2026