Returns the approval chain an automation rule produced for this request.
Stages are sequential. Within a stage, the first decision settles it for every approver on that stage, which is why every stage reports rule: any.
This is asynchronous. The chain is computed after the request is created, so a freshly raised request answers resolved: false. That means not yet, not an error — poll until resolved is true. It never returns 503.
There is deliberately no retry hint. Rule evaluation is queued work whose latency moves with organization load and rule count: chains have been measured at 34 to 106 seconds, and one request was still unresolved after four minutes. Any constant we published would be wrong often enough to mislead, and a caller that waited exactly that long and asked once more could wrongly conclude the request has no approvers. Poll on your own schedule and treat resolved: false as keep waiting, never as nobody to ask.
Check resolved before reading stages[]. An unresolved response carries an empty array, which is indistinguishable from a resolved chain with nobody on it.
no_rule_matched: true means no rule applied: the chain is empty, and the request stays pending until it is handled in Zluri, which notifies your organization's admins. This API can't approve it, but it can cancel it.
A role approver is a person — the user who holds that role — and carries role_name. When nobody holds it, unassigned: true and user_id is null: the slot exists and cannot be filled. A group is returned unexpanded with the type needed to expand it.
A closed request still resolves. This reads the chain as it stands rather than acting on it, so a cancelled, rejected or completed request answers 200: the stages keep the decisions they recorded, and current_stage is null because none is awaiting one.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
