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

# DocuSign

> DocuSign (Signature & Contract Management): the API posture, publish target and field mapping composerID publishes a decision reference through.

This page records how composerID publishes into DocuSign: the vendor's API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it.

DocuSign eSignature is the execution and evidence layer for a decision. composerID publishes an Intent as a signature Envelope, embeds the Intent ID as an envelope custom field, and tracks completion through DocuSign Connect. It is the signature step in an SoW or contingent-contract chain, not the system of record for the work itself.

<Info>
  Category: Signature & Contract Management. Coverage status: Carrier mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                                                                                                                                                                                                                                                                                                                                               |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication       | OAuth 2.0 - JWT Grant for service integrations (no user login) or Authorization Code Grant; request the signature scope.                                                                                                                                                                                                                                                                                                             |
| composerID publishes | Envelope: POST /restapi/v2.1/accounts/\{acct}/envelopes                                                                                                                                                                                                                                                                                                                                                                              |
| Intent ID lands on   | `envelope` `textCustomFields.IntentID`, written into the destination record                                                                                                                                                                                                                                                                                                                                                          |
| Carrier evidence     | Spec-checked: CI finds `customFields.textCustomFields` on `POST /v2.1/accounts/{accountId}/envelopes` in the vendor's published API specification, and returned by `GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/custom_fields`. Source: [DocuSign eSignature REST API OpenAPI specification](https://github.com/docusign/OpenAPI-Specifications/blob/master/esignature.rest.swagger-v2.1.json), checked 23 September 2026. |
| Back-sync            | Webhooks: the destination pushes events; composerID verifies each delivery and lands it on the intent's timeline.                                                                                                                                                                                                                                                                                                                    |

## Vendor documentation

<Columns cols={2}>
  <Card title="eSignature REST API Reference" icon="external-link" href="https://developers.docusign.com/docs/esign-rest-api/reference/" horizontal />

  <Card title="Authentication (OAuth 2.0)" icon="external-link" href="https://developers.docusign.com/docs/esign-rest-api/esign101/auth/" horizontal />

  <Card title="JWT Grant (service integration)" icon="external-link" href="https://developers.docusign.com/platform/auth/jwt-get-token/" horizontal />

  <Card title="Connect webhooks" icon="external-link" href="https://developers.docusign.com/platform/webhooks/connect/" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                                                                                         |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication | OAuth 2.0 - JWT Grant for service integrations (no user login) or Authorization Code Grant; request the signature scope. Auth host account.docusign.com (account-d.docusign.com demo); token at POST /oauth/token; call /oauth/userinfo once to resolve the account base\_uri. |
| Style          | REST, JSON; Authorization: Bearer                                                                                                                                                                                                                                              |
| Base URL       | https\://\{account-base-uri}.docusign.net/restapi/v2.1/accounts/\{accountId}                                                                                                                                                                                                   |
| Webhooks       | DocuSign Connect - push notifications on envelope and recipient status (sent, delivered, completed, declined, voided).                                                                                                                                                         |
| Events posture | Webhooks                                                                                                                                                                                                                                                                       |
| Rate limits    | Hourly per-account request ceilings with burst allowance; 429 with backoff. /oauth/userinfo is separately rate-limited, so cache the base\_uri.                                                                                                                                |
| Objects        | envelopes, documents, recipients (signers), tabs, templates, textCustomFields, Connect configurations                                                                                                                                                                          |

## Publish target and field mapping

Each object below pairs the canonical intent fields with the destination's own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

<AccordionGroup>
  <Accordion title="Envelope" icon="arrow-right-left" description="Create signature request from the decision">
    | Mapping                  | Detail                                                                                     |
    | ------------------------ | ------------------------------------------------------------------------------------------ |
    | Canonical to destination | defence\_file (document), signers = approvers/business\_owner, emailSubject = intent.title |
    | Target                   | POST /restapi/v2.1/accounts/\{acct}/envelopes                                              |
    | Requirement              | Required                                                                                   |
    | Notes                    | status=sent to dispatch; documents supplied as base64                                      |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Write the Intent ID onto the envelope">
    | Mapping                  | Detail                                                                  |
    | ------------------------ | ----------------------------------------------------------------------- |
    | Canonical to destination | intent\_id, intent\_version                                             |
    | Target                   | Envelope textCustomFields                                               |
    | Requirement              | Required                                                                |
    | Notes                    | Level-1 correlation - Intent ID recoverable from any completed envelope |
  </Accordion>

  <Accordion title="Completion back-sync" icon="arrow-right-left" description="Read for the intent timeline">
    | Mapping                  | Detail                                                     |
    | ------------------------ | ---------------------------------------------------------- |
    | Canonical to destination | envelope status, completedDateTime, signers\[]             |
    | Target                   | Connect webhook / GET /envelopes/\{id}                     |
    | Requirement              | Recommended                                                |
    | Notes                    | Store the completed PDF plus the certificate of completion |
  </Accordion>
</AccordionGroup>

<Note>
  eSignature is the signature/execution step, not the system of record for the underlying work - pair it with the VMS/CLM/S2P destination that owns the engagement. DocuSign now markets the broader IAM platform; composerID targets the stable eSignature REST API. Production and demo use different base hosts, so always resolve the per-account base\_uri via /oauth/userinfo.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>