Skip to main content
POST
Reject a user-delete request (checker)

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Headers

Authorization
string

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).

Path Parameters

userId
string
required

The target user whose pending delete request is being decided.

Example:

"42"

Body

application/json

Optional decision note.

note
string

Optional decision reason (≤500 chars).

Response

OK

at
string<date-time>
required

When the latest event was recorded (RFC 3339).

operator
object
required

Server-extracted operator who recorded the latest event (the maker on 'requested'; the checker otherwise).

state
enum<string>
required

Latest workflow action: 'requested' (pending a checker), 'approved' (deleted), 'rejected', or 'failed' (execution failed, retryable).

Available options:
requested,
approved,
rejected,
failed
Example:

"requested"

userId
string
required

The target user the workflow is about.

Example:

"42"

note
string

Optional operator-authored reason.

Example:

"offboarding after a role change"