Adobe Acrobat Sign

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.

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

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

Acrobat Sign v6 REST API

API Usage guide

Webhooks (OAuth 2.0)

Best practices (baseUris)

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.

Transient Document

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

Agreement

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

Intent ID correlation

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

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.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

Acrobat Sign v6 REST API

API Usage guide

Webhooks (OAuth 2.0)

Best practices (baseUris)

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

Acrobat Sign v6 REST API

API Usage guide

Webhooks (OAuth 2.0)

Best practices (baseUris)

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps