Agent Overview
image
image
The Internal Systems API specification defines how to build consistent, scalable, and secure REST APIs for any organization's internal system, like databases, data warehouses, unstructured data stores, or homegrown applications, in order to provide an interface with the DataGrail Platform to process privacy requests.
Authentication credentials must be securely stored in a supported credentials management provider and programmatically accessible to the Request Manager Agent.
Environment variables defined within the container enable dynamic configuration of all Request Manager Agent properties and operations.
The Request Manager Agent uses environment variables to configure its runtime behavior and connections. You'll need to set variables for your DataGrail domain, Agent API Key, credentials manager provider, and optionally cloud storage for handling sensitive data. This page documents all required and optional environment variables, including cloud provider credentials for local development.
Integrate Superwall with DataGrail
For many modern businesses, internal data systems are large repositories of sensitive personally identifiable information (PII). To process growing volumes of Data Subject Requests (DSR), companies must interact with every data system containing PII the organization uses, regardless of the storage medium.
IP Allowlisting lets Admins restrict platform access to specific IP ranges. You can restrict interactive sign-in for all users, restrict external MCP client connections, and separately restrict individual API keys or Agents to their own IP ranges.
image
Security Audit Logs give Super Admins a searchable record of who signed in to your DataGrail account and what they were allowed or denied to do. Use it to review failed sign-ins, investigate access, and keep evidence for security and compliance audits.
Webhook integrations allow DataGrail to dispatch privacy request processing to your systems. When a privacy request reaches the appropriate lifecycle stage, DataGrail sends an HTTP request to your webhook endpoint with the details needed to perform the work (e.g., retrieve or delete data). Once your system completes the work, it confirms completion via the provided callback URL.