List Single Policy Versions
Returns a paginated list of all versions for a single policy. Each version is a snapshot of the policy state produced by a transaction. Use this to see how a policy changed over time, or to find versions that match specific field criteria.
Example questions this endpoint answers:
- “Show me all versions of policy ABC” —
segmentScope="all", no filters - “Which versions of policy ABC had premium above $50k?” —
segmentScope="all",filterson premium field - “Which versions of policy ABC provided coverage on March 15?” —
segmentScope={"asOf":"2025-03-15"}
Query parameters (detail, segmentScope, filters, pagination, sorting) work
identically to the List Policy Versions endpoint, scoped to a single policy.
Required permission: company.policy:read
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey , and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Policy identifier
Query Parameters
Page number (1-based, default 1).
x >= 1Detail level. summary returns lightweight results with matched segment date ranges.
full includes complete field data for each scope-matched segment.
summary, full JSON-encoded segment scope filter. Controls which segments within each version
participate in filtering. Optional — defaults to "all" when omitted. Values:
"all"— every segment{"asOf":"YYYY-MM-DD"}— point-in-time{"fromDate":"YYYY-MM-DD","toDate":"YYYY-MM-DD"}— date range
JSON-encoded array of field filters. Each filter targets a field in the segment's
data object and supports type-specific operators. Supported field types:
text, number, boolean, date, currency, optionSet, address, join,
textList, numberList, optionSetList, addressList.
List-cardinality types support operators: listIncludes (textList, numberList,
addressList), listIn, listAll, listExcludes (optionSetList).
The join type supports the in operator.
See the Configuration API for available field reference IDs.
Field to sort results by
policyId, createdAt, versionCreatedAt Sort direction (default desc)
asc, desc Response
Paginated list of policy versions
Paginated list of policy results.
Why this differs from the entity list shape. A non-policy entity list
(GET /entities/{entityType}) returns flat items, each a single
{ id, fieldModelV1Data, … } record. A policy list item instead carries a
summary object (and, with detail=full, a segments array) — it has no
single top-level field-data blob. This is by design: a Policy is
a segmented entity assembled from immutable transactions, so its field
data lives per-segment rather than in one flat record. The summary gives
the policy-level view (id, full-term info, matched segment date ranges) and
segments carries the per-segment data object when requested.
