Klaviyo

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

Version

This integration utilizes the Klaviyo API v2025-04-14.

Base URL

The base URL used for all Klaviyo API endpoints:

https://a.klaviyo.com/api

---

Authentication & Authorization

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

Scopes

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

Scope	Base	Access	Deletion
profiles	✅	✅
lists		✅
segments		✅
data-privacy			✅

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	/profiles	Get all profiles in an account

---

Limits

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

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search profiles by the Data Subject email.
2. For each detected profile get profile lists.
3. For each detected profile get profile segments.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/profiles	Get all profiles in an account
GET	/profiles/profile_id/lists	Get list memberships for a profile with the given profile ID
GET	/profiles/profile_id/segments	Get segment memberships for a profile with the given profile ID

---

Deletion

DataGrail's Klaviyo 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. Request a data-privacy-compliant deletion for the person record that corresponds to the Data Subject email.
2. Search profiles by the Data Subject email to confirm deletion.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	/data-privacy-deletion-jobs	Request a deletion for the profiles.
GET	/profiles	Get all profiles in an account