Adobe Acrobat Sign

Adobe Acrobat Sign

This connector works with Adobe Acrobat Sign (formerly Adobe Sign, EchoSign) through its REST API v6 on your account's shard (https://api.<shard>.adobesign.com/api/rest/v6): agreements (find, read status, participants, events, form data, signing links, signed PDF and audit trail), creating and sending agreements from uploaded files or library templates, reminders and cancellation, library documents, web forms, users, groups, workflows and webhooks. It runs as the Acrobat Sign user who authorized it (OAuth 2.0), within that user's permissions.

Setup (about 15 minutes; an account admin creates the app)

1. Sign in to Acrobat Sign as an account admin. Note your shard from the browser address: https://secure.na1.adobesign.com/... means na1 (others: na2, na3, na4, eu1, eu2, jp1, au1, in1, sg1). Put it into ADOBE_SIGN_SHARD. Developer accounts (free, for testing) work the same way.
2. Open Account → Acrobat Sign API → API Applications, click +, give it a name and display name, and choose domain CUSTOMER.
3. Select the new application and click Configure OAuth for Application. Set the Redirect URI to https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself (https, exact match).
4. On the same page enable these scopes: user_read, agreement_read, agreement_write, agreement_send, library_read, widget_read, workflow_read, webhook_read. Pick the modifier self for a personal connector; account admins may pick account to reach every user's agreements (see Scopes). Save.
5. Click View/Edit on the application and copy the Application ID into ADOBE_SIGN_CLIENT_ID and the Client Secret into ADOBE_SIGN_CLIENT_SECRET. Install.
6. On the connector page click Authorize with Provider and sign in to Acrobat Sign. Then run adobe_acrobat_sign_get_base_uris: apiAccessPoint must contain your shard; if it shows another one, correct ADOBE_SIGN_SHARD and authorize again.

Scopes: the connector asks for user_read agreement_read agreement_write agreement_send library_read widget_read workflow_read webhook_read, which means the :self modifier: the signed-in user's own agreements, templates and web forms. An account admin who wants the AI to see the whole account can change them in the connector's OAuth settings to agreement_read:account, user_read:account and so on (the same modifiers must be enabled on the application), and authorize again. adobe_acrobat_sign_list_users needs user_read:account.

Tokens: access tokens last one hour and are renewed automatically through /oauth/v2/refresh on the shard. A refresh token unused for 60 days expires; then click Authorize with Provider again.

Workflow

• Status of an agreement: adobe_acrobat_sign_search_agreements (text, status, dates, participant email) or adobe_acrobat_sign_list_agreements, then adobe_acrobat_sign_get_agreement and adobe_acrobat_sign_get_agreement_members (who still has to sign), adobe_acrobat_sign_list_agreement_events (history), adobe_acrobat_sign_list_reminders.
• Results: adobe_acrobat_sign_get_agreement_form_data (entered values, CSV), adobe_acrobat_sign_list_agreement_documents, adobe_acrobat_sign_get_combined_document_url or adobe_acrobat_sign_download_combined_document (signed PDF), adobe_acrobat_sign_download_audit_trail (audit report PDF).
• Send for signature: upload a file with adobe_acrobat_sign_upload_transient_document (or pick a template with adobe_acrobat_sign_list_library_documents, adobe_acrobat_sign_get_library_document and adobe_acrobat_sign_list_library_document_form_fields), then adobe_acrobat_sign_create_agreement with state IN_PROCESS. Create as DRAFT and call adobe_acrobat_sign_send_agreement later to review first. adobe_acrobat_sign_get_signing_urls gives the signing link of the current signer (for in-person or embedded signing).
• Follow up: adobe_acrobat_sign_create_reminder, adobe_acrobat_sign_cancel_agreement.
• Web forms: adobe_acrobat_sign_list_web_forms, adobe_acrobat_sign_get_web_form, adobe_acrobat_sign_get_web_form_form_data, adobe_acrobat_sign_list_web_form_agreements.
• Account: adobe_acrobat_sign_get_base_uris, adobe_acrobat_sign_get_user (me for the signed-in user), adobe_acrobat_sign_list_users, adobe_acrobat_sign_list_groups, adobe_acrobat_sign_list_group_users, adobe_acrobat_sign_list_workflows, adobe_acrobat_sign_get_workflow, adobe_acrobat_sign_list_webhooks, adobe_acrobat_sign_get_webhook.

Sending is real: confirm first. adobe_acrobat_sign_create_agreement with IN_PROCESS and adobe_acrobat_sign_send_agreement email the recipients; adobe_acrobat_sign_cancel_agreement cannot be undone; reminders email people. Show the user the documents, the recipients in order and the message, and send only after a clear yes.

Creating an agreement: file_infos takes one entry per document: {"transientDocumentId": ...}, {"libraryDocumentId": ...} or {"urlFileInfo": {"url": ..., "name": ..., "mimeType": ...}} (Adobe fetches a public URL itself). participant_sets lists recipients with order (1, 2, ...) and role (SIGNER, APPROVER, ACCEPTOR, FORM_FILLER, CERTIFIED_RECIPIENT). Without signature fields in the document (text tags or template fields), Acrobat Sign adds a signature block at the end. merge_field_info pre-fills template fields by name. Transient documents expire after 7 days.

Reading the answers: agreement status is OUT_FOR_SIGNATURE, OUT_FOR_APPROVAL, SIGNED, APPROVED, ACCEPTED, FORM_FILLED, DELIVERED, CANCELLED, EXPIRED, DRAFT, AUTHORING, ... Dates are ISO 8601 in UTC. Member status such as WAITING_FOR_MY_SIGNATURE, NOT_YET_VISIBLE or COMPLETED shows each participant's step. Form data comes as CSV text. PDFs (adobe_acrobat_sign_download_combined_document, adobe_acrobat_sign_download_audit_trail) are handed over as file attachments, up to 10 MB.

Paging: list tools return page.nextCursor; pass it as cursor until it is missing. adobe_acrobat_sign_search_agreements pages with start_index (searchPageInfo.nextIndex), up to 100 results per page and 10,000 in total.

Limits: Acrobat Sign throttles API calls per user and per account depending on the plan; a 429 answer carries Retry-After (seconds).

Common errors

• 401 INVALID_ACCESS_TOKEN: the authorization expired or was revoked; authorize again. 401 right after authorizing usually means a wrong ADOBE_SIGN_SHARD.
• 403 PERMISSION_DENIED or INVALID_API_ACCESS_POINT: the scope or its modifier is missing (for example user_read:account for users), the user may not see that agreement, or the call went to the wrong shard.
• 404 INVALID_AGREEMENT_ID (or another INVALID_..._ID): wrong id, or the agreement belongs to another user and the scope is :self.
• 400 INVALID_ARGUMENTS, MISSING_REQUIRED_PARAM, INVALID_EMAIL: a field is missing or wrong; the message names it.
• 404 AGREEMENT_NOT_EXPOSED on signing URLs: the agreement is still being prepared; wait a few seconds and ask again.

Switched off at install: adobe_acrobat_sign_cancel_agreement, which cannot be undone; an admin switches it on when the team needs it.