Sift

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

Version

This integration utilizes the Sift Score and Decisions APIs v205.

Base URL

The base URL used for all Sift API endpoints:

https​://api.sift.com

---

Authentication & Authorization

The DataGrail Sift integration connects using header-based authentication which requires an API Key and Account ID.

Sensitive Credentials

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

Endpoints Utilized

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

Method	Endpoint	Purpose	Docs
GET	/v205/users/user_id/score	Validate credentials

Limits

Limits in Sift 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 Sift integration provides Synchronous Access capabilities for the following supported identifier categories: Email and User ID.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search for a user with configured data subject identifiers.
2. Retrieve the list of all Decisions and filter results by the Data Subject email.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/v205/users/user_id/score	Check for a user
GET	/v3/accounts/account_id/decisions	Retrieve the list of decisions

---