Approve a user-delete request (checker) and execute the deletion
The CHECKER approves a pending request. The checker (token sub) MUST differ from the maker (four-eyes, 403 otherwise). On approval the Cabine API executes the deletion in Access Manager with a service credential, recording ‘approved’ ONLY on success; an execution failure records ‘failed’ (retryable) and returns 502.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Bearer JWT. Must be a normal-user principal: an application token is refused with 403, and any other token type is refused with 401 at the gate. The CHECKER identity is derived from THIS token; it MUST differ from the requester (four-eyes).
Parâmetros de caminho
The target user whose pending delete request is being decided.
"42"
Corpo
Optional decision note.
Optional decision reason (≤500 chars).
Resposta
OK
When the latest event was recorded (RFC 3339).
Server-extracted operator who recorded the latest event (the maker on 'requested'; the checker otherwise).
Latest workflow action: 'requested' (pending a checker), 'approved' (deleted), 'rejected', or 'failed' (execution failed, retryable).
requested, approved, rejected, failed "requested"
The target user the workflow is about.
"42"
Optional operator-authored reason.
"offboarding after a role change"

