Skip to main content
The Prizm REST API gives you programmatic access to the same data your organization manages in the Prizm UI — assets, metrics, alerts, issues, sources, schedules, and governance entities like domains, glossaries, and tags.
This reference is in active development. Endpoint paths, methods, and groupings below are confirmed against the current API. Response field-level schemas are confirmed for 68 of 156 operations so far, captured directly from a live QA environment — every read (GET/list) operation reachable from existing records. The remaining operations are write actions (create/update/delete, intentionally not exercised against live data) or reads with no existing records to capture from yet; those pages say so explicitly rather than guessing at fields.

​
Base URL

Every request is made against your organization’s Prizm workspace host:
Replace <your-workspace> with your organization’s subdomain — the same host you use to sign in to Prizm.

​
Services

The API is organized into seven services, each with its own path prefix: This reference currently covers Create / Get / List / Update / Delete operations for each resource — auxiliary actions, statistics, and reporting endpoints will be added over time.

​
Before you start

Authentication

Generate an API access token and see how to send it with every request.

Response & Error Format

Understand the response envelope and the list/filter pattern shared across endpoints.

​
Making your first request

Every endpoint requires a bearer token (see Authentication). Here’s a minimal example against a list endpoint: