Adobe Sign

This documentation for the Adobe Sign integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Adobe Sign, visit our connection instructions.

Version

This integration utilizes the Adobe Sign REST API v6.

Base URL

The base URL used for all Adobe Sign API endpoints contains the Access point:

https://access_point/api/rest/v6

---

Authentication & Authorization

The DataGrail Adobe Sign integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Adobe Sign API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Scopes

The Adobe Sign integration requires specific scopes that must be granted in order to function for a given capability.

Scope	Base	Access
user_read:account	✅	✅
agreement_read:account	✅	✅
user_login:account	✅	✅
library_read:account	✅	✅
workflow_read:account	✅	✅
application_read:account	✅	✅

Base Scopes

All base scopes must be granted in order to connect the integration with DataGrail. The remaining scopes are only required if enabling those capabilities

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	/agreements	Validate credentials
POST	/oauth/v2/refresh	Refresh access token
POST	https://api.na1.adobesign.com/oauth/v2/token	Get access token
GET	https://secure.na1.adobesign.com/public/oauth/v2/authorize	Request authorization

---

Limits

Limits in Adobe Sign are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Adobe Sign integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Fetch all agreements.
2. Search agreements that include participants with configured identifiers.
3. For each collected agreement:
   • Fetch all members.
   • Fetch all events.
   • Fetch all documents.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/agreements	Fetch all agreements
GET	/agreements/id/documents	Fetch all documents
GET	/agreements/id/events	Fetch all events
GET	/agreements/id/members	Fetch all members

---