Adobe Acrobat Sign

Connect Adobe Acrobat Sign to collect digital signature evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Adobe Acrobat Sign:

   1. Log in to Acrobat Sign as an account admin and select API from the top menu (enterprise customers who do not see it choose Account).
   2. Select API Applications, select the Create (+) icon, describe the app and choose the domain CUSTOMER (apps that only access your own account).
   3. In API Applications, select the app and choose View/Edit to get the application ID and secret.
   4. Click Configure OAuth for the Application, enter a secure (https) redirect URL, check Enabled for each scope Safeguard needs, set its modifier to account, and choose Save.
   5. Send an admin to https://secure.echosign.com/public/oauth with response_type=code, client_id, redirect_uri and scope; on the consent page they select Allow Access. Within 5 minutes, POST the returned code with your client ID, client secret and redirect URI (grant_type=authorization_code) to the /oauth/token endpoint, and paste the access token into Safeguard.

   Where to find the other values:

   • API URL: The api_access_point returned with the OAuth code and in the token response; use it as the base URI for all subsequent calls.

   Adobe Acrobat Sign's public documentation does not cover every step.

   Not sourced: the simpler Integration Key path (Adobe's help article returned HTTP 403), which many admins use to get a long-lived token with chosen scopes. OAuth access tokens expire and must be refreshed, so a pasted OAuth access token will stop working; a refresh-token or integration-key flow is needed for lasting access. The user_read:account scope covers reading all users in the account and requires an account admin to grant it. On verification the scope name user_read, the /oauth/v2/token path and the shard examples were removed: the fetched getting-started guide does not name them and the REST v6 page rendered no readable content.

   Source: developer.adobe.com, secure.na1.adobesign.com, checked 2026-10-07.

   The permissions Safeguard needs: user_read:account. Safeguard's compliance tests for Adobe Acrobat Sign need the credential on the API token tab: an OAuth connection cannot read everything they check.

2. On Compliance › Connectors, open Adobe Acrobat Sign, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.
   API URL	Required. For example: https://api.na1.adobesign.com

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Adobe Acrobat Sign and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Digital Signature connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks