Experimental endpoint — not yet a stable contract. This action ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.

End all browser sessions, remembered browser access and application access for the target administrator. This does not disable the administrator or prevent a new sign-in.

The authenticated Public API principal is the API token's administrator. It may run this action when an administrator with the same role, permissions and organization could run it in the admin panel. The target must be a concrete human global or operator administrator; an account that belongs to an API access token cannot be the target. The action writes the same audit log entry as in the admin panel, attributed to the API token's administrator. Existing administrator-management permissions, role hierarchy and operator scope apply; another administrator is never substituted for the authenticated principal.

The accepted operation durably records its progress. A 202 response does not guarantee that both browser sessions and application access have been ended: inspect data.outcome for the actual state. Pending work is retried independently with bounded backoff, up to five total attempts including the initial attempt. If work remains after the fifth attempt, the operation becomes blocked with blockedReason set to retry_exhausted. An operation also becomes blocked if its actor or subject is unavailable. A blocked outcome includes blockedReason when available. The response never includes a session count.

No request body or includes are supported.