Policy Listing (Api-Version: 2)
GET /policies — requires Api-Version: 2 header
Returns all policies. Version 2 adds support for filtering by status and includes extended userGroups and userGroup fields in each policy object.
Authentication: Bearer token required (Authorization: Bearer <token>)
Permissions: One of:
Permissions.POLICIES_POLICY_READPermissions.POLICIES_POLICY_EXECUTEPermissions.POLICIES_POLICY_MANAGEPermissions.POLICIES_POLICY_AUDIT
Request
Headers
Api-Version
2
Yes
Enables V2 behaviour (status filter, extended user group fields)
Query Parameters
pageIndex
number
No
The number of pages to skip before starting to collect the result set
pageSize
number
No
The number of items to return
type
string
No
Policy type (e.g. local)
status
string
No
Filter by policy status. Multiple values can be passed as a comma-separated list (e.g. PUBLISH,DISCONTINUED). Allowed values: DRAFT, DRY_RUN, DEMO, PUBLISH, DISCONTINUED, FAILED
name
string
No
Filter by policy name (case-insensitive substring match, e.g. iREC)
version
string
No
Filter by exact policy version (e.g. 1.0.0)
Response
Success Response
Status: 200 OK
Returns an array of policy objects. The total item count is provided in the X-Total-Count response header.
Each policy object may include:
userGroups— all group rows for the current user on that policy, including inactive groupsuserGroup— the last active group in server order (useful for UI labels such asgroupLabeloruuid)
Behaviour by role:
Standard Registry on dry-run policies:
userRoleanduserGroupreflect the last active role (often a virtual user).userGroupscontains the group rows for that role. When the last active role is Administrator,userGroupsis[].Regular users:
userGroupsusually shows roles on published policies.
Error Responses
401 Unauthorized
Missing or invalid token
403 Forbidden
Insufficient permissions
500 Internal Server Error
Unexpected server failure
Last updated