> 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

# Best practices for building your listener

> Learn best practices for building your Connect listener.

To take best advantage of Docusign Connect, you need to have a clear understanding of how the information from Connect notifications will be used. Be sure to ask questions such as:

* What data do you want to capture?
* Who will be accessing this information?
* What decisions or reporting will be generated?
* Should the document be pushed?

The answers to these questions must be thought out and agreed in order to develop a solution that will meet your business needs.

## Tips

* Don’t send documents on every request. Most of the time developers only need the final completed document.
* Mix and match multiple configurations to minimize the data sent. For example, subscribe to "Recipient Signed" events with only the basic data, then subscribe to the "Envelope complete" event with the document included.
* If your listener received the messages, accept the message, place it into a queue, and process asynchronously. This allows your endpoint to scale in case of large influxes. or when the webhook payload size is very large.
* **Envelope-level Connect:** As part of sending the envelope, a callback URL can be included with the request for the Docusign service to call the client application whenever an event occurs for the envelope. Docusign strongly recommends that the completed document, the certificate of completion (if needed), and the document fields are included with the response in the webhook.
* **Redirect URL post-signing:** For applications that are embedding the signing experience, the most effective method to get the completion status of the envelope is to use a post-signing redirect URL. The Docusign service automatically redirects the signer to the redirect URL after they have completed signing the document. Additional parameters on the redirect URL can be used to update the status of the envelope in the external application.
* **Batched envelope status calls:** It is also possible to do a batched envelope status call. If you have cached the envelope IDs previously, you can also use the [Envelopes:listStatusChanges](/docs/esign-rest-api/reference/envelopes/envelopes/liststatuschanges) API call infrequently (once an hour, for example), in which you can pass a set of envelope IDs and Docusign will return all their statuses at once. This is much more efficient than querying one at a time. To use our batched `listStatusChanges` call, you can pass a set of envelope IDs with `from_to_status=changed` and a specific timeframe to get all envelope changes.

  If setting up a listener is not possible due to IT configuration challenges, your client application can use the API to request the status of an envelope. Calling the API for envelope status is not recommended more than once every four to six hours. More frequent calls will result in the available API capacity being consumed for status information. If your scenario requires real-time actions or notifications, use one of the above methods; otherwise, should you run into API limits, your integration may not be approved for limit increases.

## Next steps

* See how to [Implement Connect with your app](/platform/webhooks/connect/implement).
* See a list of [Webhook event triggers](/platform/webhooks/connect/event-triggers).
* Learn about [Using HMAC Security with Docusign Connect](/platform/webhooks/connect/hmac).
* Learn about [Mutual TLS](/platform/webhooks/mutual-tls).
* See [MyConnectWebhook](https://webhooks.sampleapps.docusign.com/) for a sample app demonstrating how Connect works.