Skip to main content

List Data Policy Versions

List the version history of a data policy: each version snapshots the ruleset with its status and compiled execution plan for audit and correlation.

Retrieve the version history of a data policy. Each version is a snapshot of the policy's configuration at a point in time, carrying its own status and, once compiled, the compiled execution plan. Versions are created as the policy's fields and rules are authored and revised, so the history shows how the transformation logic evolved.

Version numbers are monotonically increasing integers starting at 1, returned newest first. When a resolution run captures a policy snapshot it records the version it executed, so you can correlate resolution results with the exact configuration that produced them.

GET/v1/data-policies/{id}/versions

Path parameters

id*uuidData policy UUID.

Response

Response fields

dataarrayArray of version objects, newest first.
data[].idstringVersion UUID.
data[].version_numberintegerVersion number (monotonically increasing).
data[].statusstringVersion status (e.g. draft, active).
data[].compiled_rulesobject | nullCompiled execution plan for this version, when compiled.
data[].created_atstringISO 8601 timestamp when this version was created.
links.selfstringURL to this version list.
links.policystringURL to the parent policy.

curl

Response

{
  "data": [
    {
      "id": "v3a2b3c4-0003",
      "version_number": 3,
      "status": "active",
      "compiled_rules": { "steps": 8 },
      "created_at": "2024-10-15T11:30:00.000Z"
    },
    {
      "id": "v2a2b3c4-0002",
      "version_number": 2,
      "status": "draft",
      "compiled_rules": null,
      "created_at": "2024-10-10T14:00:00.000Z"
    }
  ],
  "links": {
    "self": "/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890/versions",
    "policy": "/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890"
  }
}

Errors

Error responses

401unauthorizedMissing or invalid API key.
404not_foundData policy not found or does not belong to your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.
A version compiles on use: when a pipeline's Resolve stage runs an uncompiled version, the platform compiles it first and persists the plan, so compiled_rules fills in the first time the version actually executes.

Related

Get Data Policy
Update Data Policy
Resolutions