A

Adobe Acrobat Sign

Productivity Bearer token

Send agreements for signature, and track their status, with Adobe Acrobat Sign from any Windmill script, flow or app.

Set up in 3 steps

1

Get an integration key

In Acrobat Sign, open Account then API then API Applications. Create an application, enable the scopes your scripts need, and create an integration key — a long-lived token.

2

Add the resource in Windmill

Open Resources, add a resource of type adobe_acrobat_sign, and paste it into token. Leave base_uri empty — the scripts discover your account's shard themselves.

3

Run your first script

Fork any script below and read before writing anything.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

adobe_acrobat_sign — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
base_uristringNoOptional. Regional API access point for the account, e.g. https://api.na1.adobesign.com (host only, no path). Leave blank to auto-discover it on each call.
tokenstringYesLong-lived Integration Key, sent as `Authorization: Bearer`. Create one in the Acrobat Sign admin under Account → Acrobat Sign API → Integration Key (your account must have Acrobat Sign API access enabled).

Questions

What is base_uri for?

Acrobat Sign splits accounts across shards, each with its own API host. Left blank, the scripts ask Adobe which one your account is on; set it only to pin a known host.

A call fails on a missing scope

Scopes are enabled on the API application, not on the key. Enable it in Acrobat Sign and create a fresh integration key.

Is my token stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.