Adobe Sign integration

Overview

Adobe Acrobat Sign (formerly Adobe Sign / EchoSign) is Adobe's e-signature platform. The Automize Adobe Sign connector covers agreements, templates, workflows, library documents, and signing groups.

• Regions: Adobe Sign is global but each Adobe organization has a shard (NA1, NA2, EU1, JP1, AU1, IN1). Base URL differs per shard – connector resolves automatically.
• Plans: Acrobat Sign Standard, Pro, Enterprise; Acrobat Pro DC includes basic Sign. API access is available on all paid plans.

Setting up the connection

Auth type: OAuth 2.0 (Authorization Code).

1. Sign in to acrobat.adobe.com → Developer → Create New API Application.
2. Choose 'OAuth 2.0' authentication.
3. Set Redirect URL to the one in the Automize Adobe Sign connector dialog.
4. Add scopes: agreement_read, agreement_write, agreement_send, library_read, user_read.
5. Copy Application ID + Application Secret.
6. In Automize, open Settings → Connectors → Adobe Sign → Add connection. Paste credentials, click Connect with Adobe, sign in.

Scopes required:

• agreement_read:account
• agreement_write:account
• agreement_send:account
• library_read:account
• user_read:account

Find your credentials at https://acrobat.adobe.com/link/apps/registry.

Rate limits

Adobe Sign enforces ~120 requests/min per access token. Connector retries 429 with Retry-After.

Data model

Adobe Sign's primitives:

    Account ─┬─ Library Documents (reusable templates)
             ├─ Workflows (multi-step routing definitions)
             ├─ Agreements (sent documents)
             │      ├─ Participant Sets (signers grouped by step)
             │      └─ Form Fields
             └─ Users

Available operations

7 operations available. Click any row to jump to its detail.

Operations

Cancel Agreement

Cancel an agreement

Tips

• Cancels an OUT_FOR_SIGNATURE agreement. comment shown in signer notification.

Create Agreement

Create and send an agreement for signing

Tips

• Build via fileInfos[] (uploaded file or library doc reference) + participantSetsInfo[] (signers per step) + signatureType (ESIGN or WRITTEN).
• Use Create Agreement From Template for reusable workflows – easier.

Download Agreement

Download a signed agreement document

Tips

• Returns combined PDF (original + signature page + audit trail).

Get Agreement

Get agreement details

Tips

• Returns agreement + status + events.
• Status flow: DRAFT → AUTHORING → OUT_FOR_SIGNATURE → SIGNED / CANCELLED / EXPIRED.

Get Signing URL

Get the URL for signing an agreement

List Agreements

List all agreements

No input parameters.

Tips

• Returns recent agreements (newest first). Use search and date filters.

List Templates

List library templates

No input parameters.

Tips

• Library documents available to the user. Filter by isDocumentRetentionApplied.

FAQ

Library Document vs Template – same thing?

Adobe's naming: Library Document is a reusable form/template with pre-defined fields. Workflows are multi-step routing definitions. Both can be used as the basis for new agreements.

Why does Create Agreement fail with 'missing required field'?

When using fileInfos[] directly, the participantSetsInfo[] structure must match exactly – order, role, email. Easier to use Create From Library Document or Template.

Sandbox / Developer accounts?

Sign up for an Adobe Developer Account at developer.adobe.com. Sandboxes get full API access without paid signup.

Related connectors

• Docusign
• Pandadoc