> ## 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.

# Adobe Acrobat Sign

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

This page records how composerID publishes into Adobe Acrobat Sign: 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.

Adobe Acrobat Sign (REST API v6) is a signature/execution layer, the same role as DocuSign. composerID uploads the decision document as a transientDocument, creates an Agreement (optionally via a predefined workflow), stamps the Intent ID as the agreement externalId, and tracks status through v6 webhooks.

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

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                                                                             |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication       | OAuth 2.0 with scoped tokens (agreement\_send, agreement\_write, agreement\_read, workflow\_read) or an Integration Key bearer token for single-tenant automation. |
| composerID publishes | Transient Document: POST /api/rest/v6/transientDocuments                                                                                                           |
| Intent ID lands on   | `agreement` `externalId`, written into the destination record                                                                                                      |
| 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="Acrobat Sign v6 REST API" icon="external-link" href="https://developer.adobe.com/acrobat-sign/docs/overview/" horizontal />

  <Card title="API Usage guide" icon="external-link" href="https://developer.adobe.com/acrobat-sign/docs/overview/developer_guide/apiusage" horizontal />

  <Card title="Webhooks (OAuth 2.0)" icon="external-link" href="https://developer.adobe.com/acrobat-sign/docs/overview/acrobat_sign_events/webhooks-oauth-2-0" horizontal />

  <Card title="Best practices (baseUris)" icon="external-link" href="https://developer.adobe.com/acrobat-sign/docs/overview/developer_guide/bestpractices" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                                                                                                                                      |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | OAuth 2.0 with scoped tokens (agreement\_send, agreement\_write, agreement\_read, workflow\_read) or an Integration Key bearer token for single-tenant automation. Partner apps need Adobe certification for multi-account access. Resolve the account api\_access\_point via GET /api/rest/v6/baseUris before other calls. |
| Style          | REST, JSON; Authorization: Bearer                                                                                                                                                                                                                                                                                           |
| Base URL       | https\://\{shard}.adobesign.com/api/rest/v6  (shard from baseUris, e.g. api.na1 / api.eu1)                                                                                                                                                                                                                                  |
| Webhooks       | v6 webhooks - subscribe to AGREEMENT\_\* events; the endpoint must echo the X-AdobeSign-ClientId header to verify; 72-hour progressive retry.                                                                                                                                                                               |
| Events posture | Webhooks                                                                                                                                                                                                                                                                                                                    |
| Rate limits    | Per-minute/hour/day limits by service level; heavy operations run async; avoid polling (risks 429 / temporary API disable) - use webhooks.                                                                                                                                                                                  |
| Objects        | transientDocuments, agreements, libraryDocuments, widgets, megaSigns, workflows, webhooks, users, groups                                                                                                                                                                                                                    |

## 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="Transient Document" icon="arrow-right-left" description="Upload the decision document">
    | Mapping                  | Detail                                                        |
    | ------------------------ | ------------------------------------------------------------- |
    | Canonical to destination | defence\_file / SoW draft (file)                              |
    | Target                   | POST /api/rest/v6/transientDocuments                          |
    | Requirement              | Required                                                      |
    | Notes                    | Returns transientDocumentId used as the agreement file source |
  </Accordion>

  <Accordion title="Agreement" icon="arrow-right-left" description="Create the signature request">
    | Mapping                  | Detail                                                                              |
    | ------------------------ | ----------------------------------------------------------------------------------- |
    | Canonical to destination | name = intent.title, participants = approvers/signers, workflowId (optional), state |
    | Target                   | POST /api/rest/v6/agreements                                                        |
    | Requirement              | Required                                                                            |
    | Notes                    | Reference the transientDocumentId; state=IN\_PROCESS to send                        |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                               |
    | ------------------------ | ---------------------------------------------------- |
    | Canonical to destination | intent\_id, intent\_version                          |
    | Target                   | agreement externalId                                 |
    | Requirement              | Required                                             |
    | Notes                    | externalId enables lookup and POST /search back-sync |
  </Accordion>
</AccordionGroup>

<Note>
  Signature/execution layer, not the system of record for the work - chain it with the owning VMS/CLM/S2P destination. Each account resolves to a regional shard, so cache the api\_access\_point from baseUris. Multi-tenant (PARTNER) apps must be Adobe-certified before acting on other accounts.
</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>