> 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

# Webhooks

> Learn about the options for tacking the status of your signature requests using webhooks and Docusign Connect.

The best way for your app to track request status is by using [Docusign Connect](/platform/webhooks/connect). Connect uses webhooks to notify your application when an event occurs that your application wants to know about. For example, your application can be notified whenever an individual recipient signs a document or when an envelope is fully signed and completed.

## Steps to use webhooks to get envelope status

You can start receiving envelope status updates in your app by:

1. Identifying how your app will use [Docusign Connect](/platform/webhooks/connect). You can configure Connect to use different message formats, sets of events to subscribe to, and even scope it to detect events on account, recipient, or individual envelopes. See [Implement Connect with your app](/platform/webhooks/connect/implement) for details.
2. Creating a custom configuration. The configuration tells Connect which events your app needs to know about, where to send its messages, which message format to use, and other settings. See [Create a custom configuration and trigger a test event](/platform/webhooks/connect/create-configuration-trigger-event) for details on how to create and test your custom configuration.

   Note that Connect configurations are defined either for the developer or production environment. When you take your app into the production environment, you will need to recreate your Connect configurations in prod.
3. Creating a webhook listener. A webhook listener is an app that you create that exposes an endpoint URL that will receive event messages from Connect. See [Create a webhook listener](/platform/webhooks/connect/create-webhook-listener) for details.

## Next steps

* Learn how to [Go-Live](/platform/go-live) for an app.
* For details about Connect, see [Docusign eSignature Admin Guide: Docusign Connect](https://support.docusign.com/s/document-item?bundleId=vob1727899215236\&topicId=ctv1583277395112.html) or [Docusign Connect](/platform/webhooks/connect).
* Explore a live demo of Docusign Connect with our [MyConnectWebhook](https://webhooks.sampleapps.docusign.com/).

> Learn about the options for tacking the status of your signature requests using webhooks and Docusign Connect.

## Docs

- [Docusign Connect overview (webhooks)](https://developers.docusign.com/platform/webhooks/connect.md): Proactively notify your application when an event occurs with the Docusign Connect notification service.
- [Implement Connect with your app](https://developers.docusign.com/platform/webhooks/connect/implement.md): Plan for how your app will implement Docusign Connect, see each required step to support, and learn about best practices and important considerations.
- [Create a custom configuration and trigger a test event](https://developers.docusign.com/platform/webhooks/connect/create-configuration-trigger-event.md): See how to create your first custom configuration, then trigger and view a test event notification message.
- [Create a webhook listener](https://developers.docusign.com/platform/webhooks/connect/create-webhook-listener.md): See guidance for how to design and implement a webhook listener.
- [Best practices for building your listener](https://developers.docusign.com/platform/webhooks/connect/build-listener.md): Learn best practices for building your Connect listener.
- [JSON SIM event model (Connect 2.0)](https://developers.docusign.com/platform/webhooks/connect/json-sim-event-model.md): Learn about the JSON SIM event model for Docusign Connect.
- [Legacy event message formats](https://developers.docusign.com/platform/webhooks/connect/legacy-message-formats.md): Learn about the legacy XML SIM and aggregate message format options for Docusign Connect.
- [Webhook event triggers](https://developers.docusign.com/platform/webhooks/connect/event-triggers.md): See the full list of event triggers that your Connect configuration can use.
- [Connect Dashboard overview](https://developers.docusign.com/platform/webhooks/connect/connect-dashboard.md): Learn about how the Connect dashboard enables you to monitor the health of your Docusign connect configurations.
- [Validation and security](https://developers.docusign.com/platform/webhooks/connect/validation-and-security.md): Learn about your options for validating webhook notification messages and other Docusign Connect security options.
- [OAuth for Docusign Connect](https://developers.docusign.com/platform/webhooks/connect/validation-and-security/oauth-connect.md): Learn how you can use OAuth for Connect to authenticate that event notification messages are from Docusign.
- [Managing OAuth credentials for multiple accounts](https://developers.docusign.com/platform/webhooks/connect/validation-and-security/managing-oauth-credentials-multiple-accounts.md): As a partner or integrator see how you can use your main account’s OAuth for Connect settings for each of your client accounts.
- [Using HMAC Security with Docusign Connect](https://developers.docusign.com/platform/webhooks/connect/hmac.md): Describes what HMAC security with Docusign Connect is, when to implement it, and best practices.
- [Managing HMAC for multiple accounts](https://developers.docusign.com/platform/webhooks/connect/managing-hmac-multiple-accounts.md): As a partner or integrator with one main account who must manage multiple client connect accounts, you can configure your client accounts to be integrator managed, enabling you to use your HMAC keys for your clients’ event messages.
- [How to set up HMAC security with your app](https://developers.docusign.com/platform/webhooks/connect/setting-up-hmac.md): See how to set up Docusign Connect HMAC security with your app.
- [How to validate an HMAC signature](https://developers.docusign.com/platform/webhooks/connect/validate.md): Describes how to implement HMAC security with Docusign Connect.
- [Recipient Connect](https://developers.docusign.com/platform/webhooks/connect/recipient-connect.md): Learn about how you can use Recipient Connect to subscribe to event notifications as an envelope recipient, rather than as a sender.
- [Organization-Level Connect](https://developers.docusign.com/platform/webhooks/connect/org-level-connect.md): Learn about how you can use Organization-Level Connect configurations and the organization Connect dashboard to quickly and easily manage all of the Connect configurations in your org at once.
- [Pause a Connect configuration](https://developers.docusign.com/platform/webhooks/connect/pause-a-configuration.md): Learn about how to pause a configuration, and about how you can use this feature to gain more control over event processing, and make it easier to perform updates, maintenance, or troubleshooting without triggering additional activity
- [Connect FAQ](https://developers.docusign.com/platform/webhooks/connect/faq.md): Get answers to your top questions about our webhook product, Docusign Connect.
- [Mutual TLS](https://developers.docusign.com/platform/webhooks/mutual-tls.md): This guide describes how mutual TLS authentication and authorization works and how your integration should implement it.
- [Troubleshooting mutual TLS](https://developers.docusign.com/platform/webhooks/mutual-tls/tls-troubleshooting.md)
- [How to configure mutual TLS for NGINX](https://developers.docusign.com/platform/webhooks/mutual-tls/mutual-tls-nginx.md): To enable the NGINX web server to request mutual TLS from Docusign Connect, follow the steps outlined in this guide.
- [How to configure mutual TLS for the Apache 2 web server](https://developers.docusign.com/platform/webhooks/mutual-tls/mutual-tls-apache2.md): This topic demonstrates how to enable an Apache 2 server to request mutual TLS from Docusign Connect.
- [How to configure mutual TLS for the F5 load balancer](https://developers.docusign.com/platform/webhooks/mutual-tls/mutual-tls-f5.md): This topic demonstrates how to enable F5 to request mutual TLS from Docusign Connect and provide access control based on the certificate's fingerprint/thumbprint.
- [SOAP interface](https://developers.docusign.com/platform/webhooks/connect/soap-interface.md): Learn how to use the Docusign Connect SOAP interface