Bulk update package status
Updates the status of multiple packages at once. The supported transitions are draft → pending and pending → revoked.
Moving packages from draft to pending makes them visible to their stakeholders so the signing flow can begin. Moving pending packages to revoked withdraws them so stakeholders can no longer act on them.
All packages in a single call must start from the same status: the update only succeeds for packages whose current status allows the requested transition. For example, mixing draft and pending packages in a request that targets revoked succeeds only for the pending packages.
When revoking, set SuppressNotifications to true to skip the revocation
notifications.
Like other bulk actions, this call is processed asynchronously and returns a bulk action session identifier; poll the package bulk action session to follow its progress.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Body
Request for bulk modify package status action
A globally unique identifier
The status the packages must be updated to. Supported transitions are draft to Pending and pending to Revoked.
Pending, Revoked When true, no notifications are sent for the status change. Only applies when Status is Revoked.
Response
An unique identifier of the created bulk action session.
A bulk action session unique identifier
"00000000-0000-0000-0000-000000000000"