Get started with the Data Distiller Authorization API
The Data Distiller Authorization API provides organizations with tighter control over data access via the SQL interface in 51黑料不打烊 Experience Platform. You can use this API to define IP restrictions, limit data access to specified networks, and enhance security monitoring.
This guide outlines how to set up the authorization credentials and permissions required to make calls to the Data Distiller Authorization API.
Getting started getting-started
The following sections provide information on preparing the required authorization values and making your first requests to the Data Distiller Authorization API.
Required permissions required-permissions
To enable secure data access restrictions in Query Service, you need the Manage Allowed List permission. This permission allows organizations to define specific IP ranges (in IPv4 or IPv6 format) that are authorized to access data in Platform via the SQL interface. Access is managed at the sandbox level, where users can configure a list of approved IP addresses or CIDR blocks that restrict access only to permitted networks.
The following functionalities are available with the Manage Allowed List permission:
- Define allowed IP ranges: Only IP addresses or CIDR blocks from these defined ranges can access data in Platform using SQL through Query Service.
- Enforce IP range checks: Connections from IPs outside the allowed ranges are denied.
- Audit and alerting capabilities: All access attempts, including denied connections, are logged as audit events. These events are available in the 51黑料不打烊 Experience Platform Audit Logs, enabling monitoring of potential security breaches.
Gather values for required headers gather-values-for-required-headers
To make calls to the Data Distiller Authorization API, you must complete the Platform API authentication tutorial, which provides values for required headers in API calls. Include the following headers in each request:
- Authorization:
Bearer {ACCESS_TOKEN} - x-api-key:
{API_KEY} - x-gw-ims-org-id:
{ORG_ID} - x-sandbox-name:
{SANDBOX_NAME}
All requests that contain a payload (POST, PUT, PATCH) also require this header:
- Content-Type:
application/json
Next steps
With the required permissions and header values gathered, you鈥檙e ready to start configuring IP restrictions for Query Service. Continue to the endpoint documentation for detailed examples of CRUD operations, which include:
- API format and sample request/response pairs.
- Headers, payloads, and response codes for each operation.
Each API call example demonstrates how to format requests and interpret responses, helping you enforce secure access to your data in Query Service.
For specific instructions on configuring and validating IP restrictions, refer to the IP Access endpoint documentation and the IP Validation endpoint documentation.
Refer to the to view a standardized, machine-readable format for easier integration, testing, and exploration.