Skip to main content

DocuSign Webhooks

This guide covers how to use ngrok to integrate your localhost app with DocuSign by using Webhooks. DocuSign webhooks can be used to notify an external application whenever specific events occur in your DocuSign account.

By integrating ngrok with DocuSign, you can:

  • Develop and test DocuSign webhooks locally, eliminating the time in deploying your development code to a public environment and setting it up in HTTPS.
  • Inspect and troubleshoot requests from DocuSign in real-time via the inspection UI and API.
  • Modify and Replay DocuSign Webhook requests with a single click and without spending time reproducing events manually in your DocuSign account.
  • Secure your app with DocuSign validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.

Step 1: Start your app

For this tutorial, we'll use the sample NodeJS app available on GitHub.

To install this sample, run the following commands in a terminal:

Loading…

This will get the project installed locally.

Now you can launch the app by running the following command:

Loading…

The app runs by default on port 3000.

You can validate that the app is up and running by visiting http://localhost:3000. The application logs request headers and body in the terminal and responds with a message in the browser.

Step 2: Launch ngrok

Once your app is running successfully on localhost, let's get it on the internet securely using ngrok!

  1. If you're not an ngrok user yet, just sign up for ngrok for free.

  2. Download the ngrok agent.

  3. Go to the ngrok dashboard and copy your Authtoken.
    Tip: The ngrok agent uses the auth token to log into your account when you start a tunnel.

  4. Start ngrok by running the following command:

    Loading…
  5. ngrok will display a URL where your localhost application is exposed to the internet (copy this URL for use with DocuSign). ngrok agent running

Step 3: Integrate DocuSign

To register a webhook on your DocuSign account follow the instructions below:

  1. Access DocuSign and sign in using your DocuSign account.

  2. In the top menu, click Settings and then click Connect under the INTEGRATIONS section of the left menu.

  3. In the Connect page, click ADD CONFIGURATION and then click Custom.

  4. On the Add Custom Configuration page, enter a name in the Name field, and in the URL to Publish field enter the URL provided by the ngrok agent to expose your application to the internet (i.e. https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). URL to Publish

  5. In the Trigger Events sections, expand Envelope and Recipients, click Envelope Sent, and then click ADD CONFIGURATION at the bottom of the page.

Run Webhooks with DocuSign and ngrok

DocuSign sends different request body contents depending on the event that is being triggered. You can trigger new calls from DocuSign to your application by following the instructions below.

  1. In the same browser, access your DocuSign inbox by clicking Manage on the top menu and then clicking START NOW.

  2. In the Upload a Document and Add Envelope Recipients page, click UPLOAD and then click Desktop.

  3. Select a document from your desktop, expand the Add recipients section and then click I'm the only signer. Tip: Optionally, you can select a user from the Name list.

  4. Click SIGN at the bottom right of the page.

    Confirm your localhost app receives the create-envelop event notification and logs both headers and body in the terminal.

Optionally, you can verify the log of the webhook call in DocuSign:

  1. Access your DocuSign account home page, and click Settings on the top menu.

  2. On the left menu, click Connect, click the LOGS tab, and then click the most recent entry in the log list. Logs

Inspecting requests

ngrok's Traffic Inspector captures all requests made through your ngrok endpoint to your localhost app. Click on any request to view detailed information about both the request and response.

info

By default, accounts only collect traffic metadata to avoid exposing secrets. You must enable full capture in the Observability section of your account settings to capture complete request and response data.

Use the traffic inspector to:

  • Validate webhook payloads and response data
  • Debug request headers, methods, and status codes
  • Troubleshoot integration issues without adding logging to your app

Replaying requests

Test your webhook handling code without triggering new events from your service using the Traffic Inspector's replay feature:

  1. Send a test webhook from your service to generate traffic in your Traffic Inspector.

  2. Select the request you want to replay in the traffic inspector.

  3. Choose your replay option:

    • Click Replay to send the exact same request again
    • Select Replay with modifications to edit the request before sending
  4. Modify the request (optional): Edit any part of the original request, such as changing field values in the request body.

  5. Send the request by clicking Replay.

Your local application will receive the replayed request and log the data to the terminal.

Secure webhook requests

The ngrok signature webhook verification feature allows ngrok to assert that requests from your DocuSign webhook are the only traffic allowed to make calls to your localhost app.

Note: This ngrok feature is limited to 500 validations per month on free ngrok accounts. For unlimited, upgrade to Pro or Enterprise.

This is a quick step to add extra protection to your application.

  1. Access your DocuSign account home page and click Settings on the top menu.

  2. On the left menu, click Connect, click the CONNECT KEYS tab, click ADD SECRET KEY, and then copy the key value generated by DocuSign.

  3. In the Connect page, click the APPLICATIONS tab, click your webhook, and then in the Integration and Security Settings section click Include HMAC Signature.

  4. Create a file named docusign_policy.yml, replacing {your connect key} with the value you copied before:

    Loading…
  5. Restart your ngrok agent by running the command:

    Loading…
  6. Access DocuSign and create a new envelope.

    Verify that your local application receives the request and logs information to the terminal.