Intrinsic
This documentation for the Intrinsic integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Intrinsic, visit our connection instructions.
Version
This integration utilizes the Intrinsic API v2.
Base URL
The base URL used for all Intrinsic API endpoints:https://intrinsicapi.com/api/v2
Authentication & Authorization
The DataGrail Intrinsic integration connects using api-key authentication which requires an API Key.
Sensitive Credentials
Publicly exposing your API credentials can allow unauthorized access to Intrinsic 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:
Limits
Limits in Intrinsic 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 Intrinsic 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 a GDPR request including the Data Subject Email.
- Check status of GDPR request.
Endpoints Utilized
Need help?
If you have any questions, please reach out to your dedicated CSM 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.