Integrating Dixa
Capabilities
DataGrail's Dixa integration provides the following capabilities:
| Product | Capability | ||||||
|---|---|---|---|---|---|---|---|
| Request Manager |
|
Before You Start
To successfully configure this integration, please ensure you have sufficient privileges:
- DataGrail User Role: Super Admin, Connections Manager
- Dixa User Role: Admin
Generate a Dixa API Token
- Contact your Dixa Admin to generate an API token.
- Copy the API Token and store it in a secure, temporary location.
Connect to DataGrail
- In DataGrail, navigate to Integrations and select Configure New Integration to search for Dixa.
- Enter the API Token.
- Select Configure Integration.
Dixa identifies data by email and phone number. The email is a default identifier, you can configure phone identifier in extracted identifiers page.
Next Steps
Now that you've successfully connected the integration, check out the following resources:
- Synchronous vs. Asynchronous Integrations
- Whole Record Deletion
- Access Request Lifecycle
- Deletion Request Lifecycle
Troubleshooting
If you are unable to successfully connect the integration, review these common troubleshooting steps:
Ensure Required Permissions Are Granted on API Keys/Resources
DataGrail checks required permissions and scopes on API keys/resources used by each integration. If all necessary permissions are not granted, new connections will fail.
Review Required Account Types and User Roles
If users do not have the necessary permissions or the minimum required user role in the connecting system, the connection to DataGrail will fail. Additionally, connections will fail if your account type does not match the one required by the integration.
See Before You Start to review these requirements.
Technical Details
The Dixa integration uses the Anonymization API:| Access Type | Synchronous |
|---|---|
| Deletion Type | Asynchronous (Whole Record) |
API Documentation
Learn more about this API implementation and DataGrail functionality in our API Integration Documentation.
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.