API Changes for Group Approvals

As part of the 2026.1 release that introduces Group Approvals, we’re making a few updates to workflow behavior and related APIs.

If you are using workflow APIs or custom integrations, we recommend reviewing any logic that:

• Assumes approvers are always individual users
• Depends on workflow archive behavior
• Parses workflow or report payloads without allowing additional fields

Removal of Archive FunctionalityLink to this section

The Archive button will no longer appear in the UI. Workflow items can no longer be manually archived.

The existing archive API endpoint ( PUT /rs/workflow-items/{request-id}/archived) has been removed.

Introduction of “Completed” Workflow StateLink to this section

Workflow items will now move automatically to a Completed state when they are:

• Approved
• Declined
• Cancelled

As a result:

• Approved, declined, or cancelled items will automatically appear in the Completed list.
• Previously archived items will also appear in the Completed list, since only completed items could be archived.

This change simplifies workflow management and reduces manual cleanup steps.

New “Group” Property in Workflow ItemsLink to this section

Workflow items now include a new property. When the approver is a group, this property will contain:

• Group name
• approverGroup identifier
• Group members

If the approver is an individual user, this property will not be present.

Detailed ChangesLink to this section

Groups API

Response Changes

GET /groups/list
GET /groups/view

New boolean property:

"approver_group": true | false

Indicates whether the group is enabled for approvals.

Request Changes

POST /groups/new
POST /groups/save

New boolean property:

"approver_group": true | false

When true, the group can be assigned as an approver in workflows.

Users API

Response Changes

GET /users/list
GET /users/view

New property:

"approver_group": "group name"

Indicates the user's group approver.

Request Changes

POST /users/new
POST /users/save

New property:

"approver_group": "group name"

Specifies the group assigned as this user’s approver. If omitted or null, individual user-based approvals apply.

Directories API

Response Changes

GET /directories/settings

New property:

"approver_group": "group name"

Request Changes

POST /directories/settings

New properties:

"approver_group": "group name"

"rec_approver_group": true | false

 

• approver_group: Assigned group approver for the directory
• rec_approver_group: Whether the group approver is applied recursively

Assets API

Response Changes

GET /assets/settings

"approver_group": "group name"

Request Changes

POST /assets/settings

"approver_group": "group name"

Files API

Response Changes

GET /files/settings

"approver_group": "group name"

Request Changes

POST /files/settings

"approver_group": "group name"

 

POST /files/submit_for_approval

"approver_group": "group name"

 

POST /files/reassign

"approver_group": "group name"

 

These endpoints now support assigning or reassigning workflow items to groups.

Pages and Assets List APIs

Response Changes

GET /assets/list
GET /files/list

"has_approver_group_access": true | false
"locked_by_group": "group name"

• has_approver_group_access indicates whether the current user has approval permissions via group membership.
• locked_by_group returns the group name if the item is locked due to a group approval state.

These fields allow clients to properly reflect group-based approval state in list views.

Custom Reports API Changes

Group approver data can now be included in custom reports via query parameters.

Users Report

GET /reports?report=users

Query parameter:

u_approver_group=on

 

New response field:

"u_approver_group": "group name"

 

Groups Report

GET /reports?report=groups

Query parameter:

g_approver_group=on

 

New response field:

"g_approver_group": "group name"

Directories Report

GET /reports?report=directories

Query parameter:

d_approver_group=on

 

New response field:

"d_approver_group": "group name"

Pages Report

GET /reports?report=pages

Query parameter:

p_approver_group=on

 

New response field:

"p_approver_group": "group name"

Products Report

GET /reports?report=products

Query parameter:

pd_approver_group=on

 

New response field:

"pd_approver_group": "group name"

Assets Report

GET /reports?report=assets

Query parameter:

a_approver_group=on

 

New response field:

"a_approver_group": "group name"

Subscribers Report

GET /reports/subscribers

New response field:

"approvergroup": "group name"