Agent skill

DocuSign Webhooks Skill

Receive and verify DocuSign Connect webhooks. Use when setting up DocuSign webhook handlers, debugging HMAC signature verification of the X-DocuSign-Signature-1 header, or handling eSignature events like envelope-sent, envelope-completed, and recipient-completed.

Install this skill

npx skills add hookdeck/webhook-skills --skill docusign-webhooks

When to Use This Skill

Setting up DocuSign Connect webhook handlers
Debugging DocuSign HMAC signature verification failures
Understanding DocuSign envelope and recipient event types and payloads
Handling envelope-completed, recipient-completed, or other Connect events
Verifying the X-DocuSign-Signature-1 header

Verification (core)

DocuSign Connect signs the raw request body with HMAC-SHA256 keyed on your Connect HMAC secret and sends the digest as base64 in X-DocuSign-Signature-1. When multiple HMAC keys are active it sends one header per key (X-DocuSign-Signature-1, X-DocuSign-Signature-2, … up to 100); only one needs to match. The x-authorization-digest header names the algorithm (HMACSHA256). This is not the Standard Webhooks spec. The event type lives in the JSON body's event field (e.g. envelope-completed), not in a header.

Node:

const crypto = require('crypto');

// Collect every X-DocuSign-Signature-N header; any match = authentic.
function verify(rawBody, headers, secret) {
  const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('base64');
  const signatures = Object.keys(headers)
    .filter((h) => h.toLowerCase().startsWith('x-docusign-signature-'))
    .map((h) => headers[h]);
  return signatures.some((sig) => {
    try {
      return crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected));
    } catch {
      return false; // length mismatch = not a match
    }
  });
}

Python:

import hmac, hashlib, base64

def verify(raw_body: bytes, headers, secret: str) -> bool:
    expected = base64.b64encode(
        hmac.new(secret.encode(), raw_body, hashlib.sha256).digest()
    ).decode()
    sigs = [v for k, v in headers.items() if k.lower().startswith("x-docusign-signature-")]
    return any(hmac.compare_digest(sig, expected) for sig in sigs)

Important: Verify against the exact raw body bytes DocuSign sent. Any re-serialization (pretty-printing, JSON round-trip) changes the bytes and breaks the signature.

For complete handlers with route wiring, event dispatch, and tests, see:
examples/express/
examples/nextjs/
examples/fastapi/

Common Event Types

DocuSign Connect events use a hyphenated resource-action format in the JSON event field:

Event	Triggered When
`envelope-sent`	Envelope emailed to a recipient
`envelope-delivered`	Recipient opened the envelope
`envelope-completed`	All recipients completed (signed)
`envelope-declined`	A recipient declined to sign
`envelope-voided`	Sender voided the envelope
`recipient-sent`	Notification sent to a recipient
`recipient-delivered`	Recipient opened their documents
`recipient-completed`	Recipient finished their actions
`recipient-declined`	Recipient declined to sign
`recipient-authenticationfailed`	Recipient failed authentication

For the full event list, see references/overview.md and the Connect event triggers docs.

Environment Variables

DOCUSIGN_HMAC_SECRET=your_connect_hmac_secret   # From eSignature Admin > Connect > keys

Local Development

# Start tunnel (no account needed)
npx hookdeck-cli listen 3000 docusign --path /webhooks/docusign

Use the printed URL as the URL to publish to on your Connect configuration.

Reference Materials

references/overview.md - DocuSign Connect concepts and full event list
references/setup.md - Configure Connect and get the HMAC secret
references/verification.md - Signature verification details and gotchas