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.

Drift

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

Version

This integration utilizes the Drift API v1.7.

Base URL

The base URL used for all Drift API endpoints:
https://driftapi.com

Authentication & Authorization

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

Scopes

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

ScopeAccessDeletion
all_contact_read
contact_read
conversation_read
contact_write
gdpr_write

Endpoints Utilized

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


Limits

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

Data Interactions

For Access requests, DataGrail will take the following actions:

  1. Retrieve contacts using the Data Subject email.
  2. List and select conversations related to the contacts collected in the previous step.
  3. Get detailed information about a particular conversation related to collected contacts.

Endpoints Utilized


Deletion

DataGrail's Drift integration provides Asynchronous (Whole Record) Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

  1. Erase all data for all collected contacts and users.
  2. Retrieve contacts by the Data Subject email to confirm deletion.

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.