Mark a request completed or deprovisioned

For lifecycle changes that happen outside Zluri, which only your system can know about.

Two values, deliberately. Every other status Zluri derives for itself — approval outcomes from the approvals endpoint, provisioning outcomes from its workflow engine — and accepting them here would let a ticket disagree with what actually happened.

This exists for the case that matters: an application Zluri cannot provision, granted by hand, and marked done on the ticket.

Allowed transitions: completed from approved, auto-approved or prov-failed; deprov-completed from completed or deprov-failed. Anything else is INVALID_STATE_TRANSITION.

A pending request can't be marked completed. Approval happens in Zluri: an approver decides, either in Zluri or recorded by your system through approvals/record, or an automation rule approves it. If an application's approvals happen entirely in your own system, ask your Zluri admin for an automation rule that auto-approves its requests, then mark each one completed here once access is granted. When no rule matched (no_rule_matched), the request waits for your admins in Zluri; this API can't approve it.

To cancel, use the cancel endpoint — it has different authority and different side effects.

updated_by must be an organization admin or owner; anyone else is refused with 403 FORBIDDEN. An API key identifies an organization, not a person, so this check confirms that the person named may do this, not that they did. Your system must authenticate its own user and send only that user's Zluri id. Note POST /v2/users does not expose role, so the set of eligible actors has to come from your own configuration for now.

updated_by must also be active. An inactive, suspended, expired or archived person is refused with 400 USER_NOT_ACTIVE before the request is read, whatever their role.

The state is checked before the role. A request in a state the transition does not allow answers 409 INVALID_STATE_TRANSITION whoever updated_by is — so a non-admin naming a pending request sees the 409, not 403 FORBIDDEN. A 409 is therefore not a sign that updated_by was accepted: fix the state, retry, and read the next answer.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The request's request_id (REQ-1042) or its id — both are accepted.

Body Params
string
enum
required
Allowed:
string
required
^[a-fA-F0-9]{24}$

Zluri user id. Must be an administrator or owner.

string
length between 1 and 400

Why you are setting this status. Recorded with the change.

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json