Using the API

What to expect

Protegrity API Playground features functionality derived from the original suite of Protegrity products in a form of API calls. Our API endpoints are easy-to-use and ask for minimal configuration. The Playground divides available endpoint portfolio into the following families:

  • Data Protection endpoints, covering sensitive data protection. Users can decide to transform various data types, from numbers, strings, and dates without any inherent logic tom specific PII attributes like postcodes, or social security numbers.
  • Sensitive Data Discovery endpoints, which allow users to detect and classify sensitive data within payloads.
  • GenAI Security endpoints that combine the capabilities of the above, allowing users to perform automatic discovery and protection of sensitive data and specify their risk tolerance.
  • Private endpoints low-level APIs that are the closest to the actual product experience, allowing for high customization. We suggest using the private endpoints for conducting PoCs in house – with Protegrity’s Professional Services guidance. The endpoints are disabled to all users by default and are available upon request only.

Note: Protegrity does not store any data received from external API requests.

Watch the video below to learn how to use the API Playground:


Usage & Limitations

Limits of the API

Required Headers

Required authentication headers

Users and Roles

Built-in users and roles to impersonate

Sensitive Data Discovery Endpoints

Detecting sensitive information

Data Protection Endpoints

Protecting names, addresses, and other PII information

GenAI Security Endpoints (Preview)

Automatic detection & protection of sensitive data

Private Endpoints

Endpoints dedicated to running PoCs



Last modified February 19, 2025