Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

Docusign

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

Version

This integration utilizes the Docusign eSignature REST API v2.1.

Base URL

The base URL used for all Docusign API endpoints:
https://account.docusign.com/restapi/v2.1

Authentication & Authorization

The DataGrail Docusign 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 Docusign API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Scopes

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

ScopeBaseAccessDeletion
openid
impersonation
extended
signature
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:


Limits

Limits in Docusign 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 Docusign integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

  1. Search account envelopes containing the data subject email updated in the last 5 years.
  2. Filter search to collect recipients related to the data subject email data. Drop all other recipients.
  3. Fetch all account contacts.
  4. Filter contact list by data subject email.

Endpoints Utilized


Deletion

DataGrail's Docusign integration provides Synchronous Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

  1. Delete a contact associated with an account.
  2. Delete a recipient from “draft” or “sent” envelopes. If the envelope is "In Process" (has been sent and is not completed or voided), recipients that have completed their actions cannot be deleted.

Endpoints Utilized


 

Need help?
If you have any questions, please reach out to your dedicated Account Manager or contact us at support@datagrail.io.

Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.