Immuta V2 API

Policy as code benefits

• Reduces complexity: The data source API has been simplified to only require the connection information in most instances and one endpoint for all database technologies.

• Maintains less state: Whether updating or creating, the same endpoint is used, and the same data is passed. No ids are required, so no additional state is required.

• Requires fewer steps: Only an API key is required; no additional authentication step is required before using the API.

• Integrates with Git: Define data sources and policies in files that can be tracked in Git and easily pushed to Immuta. Both JSON and YAML are supported for more flexibility. (For example, use YAML to add comments in files.)

Endpoints and details

All of the API endpoints described below take either JSON or YAML, and the endpoint and payload are the same for both creating and updating data sources, policies, projects, and purposes.

• /api/v2/data

• /api/v2/policy

  • Data policies

  • Subscription policies

• /api/v2/project

• /api/v2/purpose