Inflection

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

Version

This integration utilizes the Inflection Erasure API v1.

Base URL

The base URL used for all Inflection API endpoints:

https://core-integrations.inflection.io/v1

Endpoints Utilized

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

Method	Endpoint	Purpose	Docs
POST	/erasure/persons	Validate credentials

---

Authentication & Authorization

The DataGrail Inflection integration connects using token authentication which requires an API Token.

Sensitive Credentials

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

---

Limits

Limits in Inflection 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

Deletion

DataGrail's Inflection 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:

Submit an OpenDSR erasure request.

info

Created request will be shown in Inflection UI under Settings > Erasure Requests.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	/erasure/persons	Submit an OpenDSR erasure request

---