Adobe Sign

Implementation Summary

Ethyca uses the following endpoints in Adobe Sign to retrieve and delete Personally Identifiable Information (PII) when a user submits a data subject request. See below for a summary of what Ethyca does with each endpoint:

EndpointUser Can DownloadUser Can Delete

Because Adobe Sign is an e-signatures tool, it stores PII about your customers. Keep this in mind when you are setting the DSR Customization as it will impact what is returned in your subject's DSR package.

AdobeSign may retain some information about users in their API Request Logs that will not be deleted initially. To help manage this, you may leverage AdobeSign's Data Governance features, where you are able to specify retention policies for documents and their corresponding Request Logs.

If this aligns with your use of Adobe Sign, please proceed to the next section to begin setting up your integration in the Control Panel.

For any questions, please reach out to your dedicated Customer Success Manager.

Connection Settings

To connect your instance of Adobe Sign to Ethyca, you will need to enter your Refresh Token, Client ID, and Client Secret. To locate these values, follow the steps below:

Create An Application

To use Adobe Sign APIs, you need to first create an application. Adobe Sign uses the OAuth authentication protocol to authorize requests for any Sign API endpoint.

1. Log in to Adobe Sign at

2. Select "API" from the top menu. If you are already an Enterprise customer, you may not see the API link. In that case, click Account to proceed.

3. Select "API Applications"from the left navigation.

4. Select the (+) icon to create a new application.

5. Give your new app a memorable name, such as Ethyca Privacy management. Select your domain:

  • CUSTOMER: Apps for internal use and testing. Use this domain if you need your app to access data only from your account.
  • PARTNER: Apps for production and public use. Use this domain if you need your app to access data in any Adobe Sign account.

After you have entered your app details, click the "Save" button.

Configure OAuth for the Application

Now, you must configure OAuth for your application so that the client-side applications that you build can invoke the Sign APIs.

1. Select "API Applications" from the left navigation

2. Select your app from the table. Click "View/Edit" to view your Application ID and Client Secret.

3. The window will show your Application ID and Client Secret. Enter the Application ID into the Client ID field in Ethyca. Enter the Client Secret into the Client Secret field in Ethyca. Note down Application ID and Client Secret, as you will be using this information to issue access tokens in the Adobe Sign API in a later step.

4. Select "Configure OAuth for Application". Enter into the Redirect URI field. Select the following scopes:

  • user_read
  • user_write
  • user_login
  • agreement_read
  • agreement_write
  • agreement_send
  • application_write

Locate Your Refresh Token

1. Copy and paste the URL (shown below) into a browser. You will need to change the following:

  • <shard>: to find which shard you are on, refer to the URL when you are logged in to your Adobe Sign account. In the example below, the shard is na3

  • <application_ID>: copy and paste the Application ID from the AdobeSign API application you created

This is the URL:


2. You will be prompted to log in to Adobe Sign again. Use your credentials and log in.

3. Click on "allow access". Your browser will redirect to a 500 Internal Server Error page. The page will have a URL like this one:<REFRESH TOKEN>

This URL contains your Refresh Token at the end. Copy and paste your Refresh Token into Ethyca.

When you've finished adding your connection details, you can move on to the next two tabs to configure your DSR Customization settings and complete your Data Mapping.