> 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/).