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 run 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.
A policy has a version from birth: creating a policy over the API mints version 1 as a draft in the same transaction, so this list is never empty for a policy you created. Authoring forks the current version when needed and appends new rows as the logic is revised; the policy's current-version pointer decides which configuration GET /v1/data-policies/{id} inlines and which one a new resolution executes.
Use the history for audit and correlation rather than rollback: the API cannot re-activate an old version directly. To pin behavior, record the version number your integration was validated against and alert when a newer version appears; to restore old behavior, re-author the old configuration, which appends a fresh version rather than mutating history.
/v1/data-policies/{id}/versionsPath parameters
Response
Response fields
curl
curl -s https://api.talonic.com/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890/versions \
-H "Authorization: Bearer tlnc_your_api_key"Response
{
"data": [
{
"id": "v3a2b3c4-0003",
"version_number": 3,
"status": "active",
"compiled_rules": { "steps": 8 },
"compile_status": "ok",
"compiled_at": "2024-10-15T11:31:00.000Z",
"dirty": false,
"created_at": "2024-10-15T11:30:00.000Z"
},
{
"id": "v2a2b3c4-0002",
"version_number": 2,
"status": "draft",
"compiled_rules": null,
"compile_status": null,
"compiled_at": null,
"dirty": true,
"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
compiled_rules fills in the first time the version actually executes.Frequently asked questions
How do I see which version a resolution used?+
policy_snapshot captured on a resolution run records the configuration it executed. Compare it with this version list to identify which version was active when the resolution ran.Can I roll back to a previous version?+
What is in compiled_rules?+
Why does a brand-new policy already have a version?+
draft) atomically with the policy itself, and every downstream edit resolves the editable version from that row — a policy without a version would be uneditable. The version list therefore always starts at 1.