> ## Documentation Index
> Fetch the complete documentation index at: https://grandcentral.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> E-signature connectivity with DocuSign through Grand Central

The DocuSign Connector provides connectivity with [DocuSign](https://www.docusign.com/) for e-signature through Grand Central. It helps financial institutions streamline the signing and approval of critical documents, such as contracts, within a secure, compliant, and user-friendly workflow.

**Version supported:** 2.1

## Key capabilities

<CardGroup cols={2}>
  <Card title="e-signature" icon="pen-fancy">
    Ensure compliance with audit trails and legally binding e-signatures, giving both your team and your customers peace of mind.
  </Card>

  <Card title="Embedded e-signature" icon="pen-to-square">
    Integrate the signing experience directly within your app, so customers can review and sign documents without leaving your UI.
  </Card>

  <Card title="Advanced e-signature" icon="pen-to-square">
    An Advanced Electronic Signature creates a secure link between a verified signer and a specific document, so you can verify the document still matches the version from the moment of signing.
  </Card>

  <Card title="Webhook events" icon="bell">
    Receive real-time notifications when a signer completes, declines, or views a document, or when the overall signature request status changes.
  </Card>
</CardGroup>

***

## Supported operations

The DocuSign Connector supports the following operations from the Grand Central Unified API:

### Outbound

The following table lists the outbound operations:

| Operation                     | Endpoint                                                        |
| :---------------------------- | :-------------------------------------------------------------- |
| Generate a signing request    | `POST {CORRESPONDENCE_BASE_URL}/documents/signature`            |
| Request a signing session URL | `POST {CORRESPONDENCE_BASE_URL}/sign-document/signing-sessions` |

<Note>
  Replace `{CORRESPONDENCE_BASE_URL}` with the Correspondence API base URL provided by the Grand Central team during setup.
</Note>

### Inbound (webhook)

The following table lists the inbound webhook operations:

| Operation                                | Endpoint                                                              |
| :--------------------------------------- | :-------------------------------------------------------------------- |
| Receive DocuSign signing status callback | `POST {CORRESPONDENCE_INBOUND_BASE_URL}/webhooks/documents-signature` |

<Note>
  Replace `{CORRESPONDENCE_INBOUND_BASE_URL}` with the Correspondence inbound API base URL provided during setup. Register this URL in your DocuSign Connect configuration to receive signing status updates.
</Note>

***

## Event-driven architecture

The DocuSign connector includes inbound webhook support for real-time signing status processing. The inbound connector transforms DocuSign Connect events into a unified event payload and publishes them to SyncHub for consumption by downstream systems.

For event mapping details, see [Reference](/connectors/kyc-kyb/docusign/reference).