DataGrail Integration Types

Have more questions? Submit a request

DataGrail offers integration with 1200+ systems. How we integrate with these systems can vary based on the system itself and the permissions granted to access their API. This article will explain the different ways DataGrail connects to systems and help customers make a connection type decision that's best for them.


Integration Types

API (Application Programming Interface)

An API is a connection between two or more applications that allows those systems to exchange data in an automated way. DataGrail partners with many companies to build connections with their public facing APIs to automatically complete the extraction (for Access requests), deletion, etc. for Data Subject Requests (DSRs). 

If a vendor has a public API available that DataGrail has built to, customers can connect their instance in DataGrail by supplying specific API credentials, that typically the system admin will provide, within the DataGrail platform.

Vendors are searchable on the Integrations page within the DataGrail Platform and should they have API functionality available, there will be a prompt to provide the specific credentials (with instructions of how to capture by clicking on "Get Help"), as shown in the image below. 


As a note, API integrations will also provide the option to Disable Deletion for deletion requests. DataGrail does not provide legal advice and recommends seeking legal counsel to confirm the right selection for each customer.


To learn more about our API workflows, check out this Access Lifecycle article and Deletion Lifecycle article.

Note : All vendors that DataGrail builds APIs with, own the technology on their side, thus DataGrail is consistently testing our connection to ensure proper functionality, however cannot guarantee there will never be outages or issues. If issues occur, DataGrail will immediately partner with the vendor to resolve.

Additionally, not all vendors offer a public facing API that can be built to. In this scenario, we recommend connecting the Direct Contact integration, covered below.


Asynchronous Integration

An Asynchronous (Async) Integration is still considered an API integration in that it is automated. The most notable difference is the time this type of integration takes to complete the requested action. API Integrations react almost instantaneously, whereas Async Integrations may take up to 14 days to complete the action. Whether the system is an API or Async integration is determined by the vendor.

Async integrations will require the same type of permissions and credentials to successfully connect within DataGrail


Direct Contact Integration

Direct Contact Integrations are an integrated email workflow that includes internal or external parties to process requests and can be connected for vendors without a workable API and/or for customers that prefer an alternate option to a fully automated approach.

In this case, an Email Processor (internal or external) address would be provided within the Direct Contact Integration (as shown in the image below) and would be automatically sent a link to complete the action of the DSR.


To learn more about Direct Contact Integrations and workflows, check out this Direct Contact Integration Explained article and this Direct Contact Integration Data Collection Process article.


Hybrid Integration

Hybrid Integrations are a single integration that can allow for both API and Direct Contact workflows. Some vendors do not build their public facing APIs to action Deletion requests, thus DataGrail has built a new integration type to ensure customers can still remain compliant through that vendor. In this scenario, Access requests will allow for API Integration while Deletion requests would show the option for Direct Contact Integration. Hybrid Integrations will require the same permission types as an API Integration while also requiring the same information as a Direct Contact Integration, as shown in the image below.




If you have any questions about this feature, please reach out to your dedicated CSM or


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.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful