Adobe Acrobat Sign | Operate As Docs

Connect your client's Adobe Acrobat Sign with a sign-in, and call its API through Operate As.

Website: adobe.com
Connects by: Signing in with Adobe Acrobat Sign
Category: Files and docs
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Adobe Acrobat Sign	`adobe-acrobat-sign`	`https://api.{shard}.adobesign.com/api/rest/v6`

Your client also types their shard (In your Acrobat Sign address, such as na1 in secure.na1.adobesign.com).

Connecting

Your client presses Connect on their link and approves on Adobe Acrobat Sign's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "adobe-acrobat-sign"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "adobe-acrobat-sign"    ]  }]

Permissions

What the client reads	Permission it asks for
See your Acrobat Sign profile	`user_read:self`
See your agreements and their status	`agreement_read:self`
Create and change your agreements	`agreement_write:self`
Send agreements for signature	`agreement_send:self`
See your document templates	`library_read:self`

Pass-through

Adobe Acrobat Sign has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

Add the client

In Clients, add your client and select Adobe Acrobat Sign. Then send them their link.

Your client connects

They sign in with Adobe Acrobat Sign and approve.

Find the endpoint

Pick the call from Adobe Acrobat Sign's own API docs. Your path is everything after https://api.{shard}.adobesign.com/api/rest/v6, with the parts in braces filled in from your client's account.

Send it through Operate As

Use the client's ID, the service key adobe-acrobat-sign and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../adobe-acrobat-sign/agreements" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../adobe-acrobat-sign/agreements" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Adobe Acrobat Sign refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Adobe Acrobat Sign access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Adobe Acrobat Sign access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "adobe-acrobat-sign",
    "services": [
      "adobe-acrobat-sign"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "adobe-acrobat-sign",    "services": [      "adobe-acrobat-sign"    ],    "reconnectUrl": "https://…"  }}