AI DLP Presets API

Endpoints

• List AI DLP Presets - List built-in and custom DLP presets
• Get AI DLP Preset - Get a single DLP preset by name
• Create AI DLP Preset - Create or update a custom DLP preset (upsert)
• Update AI DLP Preset - Update an existing custom DLP preset
• Delete AI DLP Preset - Delete a custom DLP preset

Authentication

All endpoints require authentication using a Personal API Access Token.

Permissions

• Admin Only - All endpoints require admin privileges (sysAdmin user or a user with the ADMIN role). Presets are a platform-level catalog; a project-scoped AI_DEVELOPMENT token is not sufficient.

Project-Scoped Surface

Besides the admin/global endpoints above (/apiops/settings/ai-dlp-presets/...), the same DLP preset family is also exposed under a project-scoped path, so a project's own AI_DEVELOPMENT token can read the effective preset catalog and manage its own custom presets without needing platform ADMIN privileges:

GET    /apiops/projects/{projectName}/ai-dlp-presets/
GET    /apiops/projects/{projectName}/ai-dlp-presets/{presetName}/
POST   /apiops/projects/{projectName}/ai-dlp-presets/{presetName}/
PUT    /apiops/projects/{projectName}/ai-dlp-presets/{presetName}/
DELETE /apiops/projects/{projectName}/ai-dlp-presets/{presetName}/

Same 5-endpoint shape, request/response bodies and field surface as the admin endpoints documented on this page — only the base path, scope resolution and permission differ:

	Admin surface (/apiops/settings/...)	Project surface (/apiops/projects/{projectName}/...)
Scope resolution	Optional ?projectId= query parameter (default admin/global scope)	{projectName} path segment, resolved to the caller's own project — never a query parameter
Permission	System admin (sysAdmin user or ADMIN role)	AI_DEVELOPMENT + VIEW (read) / MANAGE (write) in the project
Read visibility	Presets in the resolved scope only	Union of built-in presets ∪ admin-shared custom presets ∪ this project's own custom presets
Write visibility	Any non-built-in preset in the resolved scope	Only presets this project owns. A name that only resolves to a built-in or admin-shared preset is treated as not existing for this project: POST creates a new project-owned preset (and fails on the name collision), while PUT/DELETE report the preset as not found
Built-in presets	Read-only	Read-only

The admin ?projectId= surface is unchanged by this addition and stays fully backward compatible; its permission requirement is not widened.

Related Documentation

• Authentication Guide - How to obtain and use API tokens
• Error Handling - Error response formats
• AI Privacy Presets API - Manage AI privacy (PII) presets
• AI Prompt-Guard Presets API - Manage AI prompt-guard presets
• AI Gateway Settings API - Global AI Gateway settings