DocuSign | Operate As Docs

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

Website: docusign.com
Connects by: Signing in with DocuSign
Category: Files and docs
Services: 1
Tools: 394

Service	Key	Base URL
DocuSign	`docusign`	`{base_uri}/restapi/v2.1/accounts/{account_id}`

Connecting

Your client presses Connect on their link and approves on DocuSign'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": [
      "docusign"
    ]
  }
]

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

Permissions

What the client reads	Permission it asks for
Send documents for signature and see where they stand	`signature`

Tools

Install DocuSign's typed package for your language:

pip install operate-as-docusign

pip install operate-as-docusign

Run docusign.account_custom_fields_delete_account_custom_fields

curl -X POST https://api.operate.as/v1/actions/docusign.account_custom_fields_delete_account_custom_fields \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "custom_field_id": "<custom_field_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/docusign.account_custom_fields_delete_account_custom_fields \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "custom_field_id": "<custom_field_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/docusign.account_custom_fields_delete_account_custom_fields

Response

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

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

Pass-through

Paths continue from {base_uri}/restapi/v2.1/accounts/{account_id}, with the parts in braces filled in from your client's account. 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-.../docusign/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../docusign/..." \  -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 DocuSign 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 DocuSign access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's DocuSign 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": "docusign",
    "services": [
      "docusign"
    ],
    "reconnectUrl": "https://…"
  }
}

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