> 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

# Connect Category

The Connect service enables your application to be called via
HTTPS when an event of interest occurs.

Use the Connect service to "end the polling madness." With
Connect, there is no need for your application to poll Docusign
every 15 minutes to learn the latest about your envelopes.

Instead, you register your interest in one or more types of
envelope or recipient events. Then, when an interesting event
occurs, the Docusign platform will contact your application with
the event's details and data. You can register interest in
envelopes sent by particular users in your account, or for
envelopes sent by any user.

Connect can empower your organization to manage document actions
as they occur, and allows you to track their changes within your
own systems. Upon completion, envelope information, including
document content, can be stored in your own databases or CMS
systems, and these events can be triggered via webhooks
delivering messages to your application.

**Note:** To make API calls to any of the Connect endpoints, you must be an account administrator.

## Incoming Connect Calls

To use the Connect service, your application needs to provide an
HTTPS URL that can be called from the public Internet. If your
application runs on a server behind your organization's firewall,
then you will need to create a "pinhole" in the firewall to allow
the incoming Connect calls from Docusign to reach your
application. You can also use other techniques such as proxy
servers and DMZ networking for receiving the incoming calls.

Connect delivers events over HTTP requests in JSON or XML.
See [Docusign Connect overview](/platform/webhooks/connect).

If your application is not configured to accept post messages,
Docusign will NOT return an additional post error response to
your listener application. If you've enabled logging on your
configuration, it will be logged in Admin under the configuration
failure log.

## Per-envelope Connect Configuration

Instead of registering a general Connect configuration and
listener, an individual envelope can have its own Connect
configuration. See the
[`eventNotification`](/docs/esign-rest-api/reference/envelopes/envelopes/create#schema__envelopedefinition_eventnotification)
property for envelopes.

## Historical Publish Endpoint

To submit existing envelopes to an endpoint, use the [EnvelopePublish](/docs/esign-rest-api/reference/envelopes/envelopepublish) resource.

## [ConnectConfigurations](/docs/esign-rest-api/reference/connect/connectconfigurations)

**Description**

Contains information about a Docusign Connect configuration.

**Methods supported**

* [create](/docs/esign-rest-api/reference/connect/connectconfigurations/create)
* [createConnectOAuthConfig](/docs/esign-rest-api/reference/connect/connectconfigurations/createconnectoauthconfig)
* [createConnectSecret](/docs/esign-rest-api/reference/connect/connectconfigurations/createconnectsecret)
* [delete](/docs/esign-rest-api/reference/connect/connectconfigurations/delete)
* [deleteConnectOAuthConfig](/docs/esign-rest-api/reference/connect/connectconfigurations/deleteconnectoauthconfig)
* [deleteConnectSecret](/docs/esign-rest-api/reference/connect/connectconfigurations/deleteconnectsecret)
* [get](/docs/esign-rest-api/reference/connect/connectconfigurations/get)
* [getConnectAllUsers](/docs/esign-rest-api/reference/connect/connectconfigurations/getconnectallusers)
* [getConnectOAuthConfig](/docs/esign-rest-api/reference/connect/connectconfigurations/getconnectoauthconfig)
* [getConnectSecret](/docs/esign-rest-api/reference/connect/connectconfigurations/getconnectsecret)
* [list](/docs/esign-rest-api/reference/connect/connectconfigurations/list)
* [listUsers](/docs/esign-rest-api/reference/connect/connectconfigurations/listusers)
* [update](/docs/esign-rest-api/reference/connect/connectconfigurations/update)
* [updateConnectOAuthConfig](/docs/esign-rest-api/reference/connect/connectconfigurations/updateconnectoauthconfig)

## [ConnectEvents](/docs/esign-rest-api/reference/connect/connectevents)

**Description**

Connect event logging information. This object contains sections for regular Connect logs and for Connect failures.

**Methods supported**

* [delete](/docs/esign-rest-api/reference/connect/connectevents/delete)
* [deleteFailure](/docs/esign-rest-api/reference/connect/connectevents/deletefailure)
* [deleteList](/docs/esign-rest-api/reference/connect/connectevents/deletelist)
* [get](/docs/esign-rest-api/reference/connect/connectevents/get)
* [list](/docs/esign-rest-api/reference/connect/connectevents/list)
* [listFailures](/docs/esign-rest-api/reference/connect/connectevents/listfailures)
* [retryForEnvelope](/docs/esign-rest-api/reference/connect/connectevents/retryforenvelope)
* [retryForEnvelopes](/docs/esign-rest-api/reference/connect/connectevents/retryforenvelopes)