`GET /api/workflows/pending-approvals` — the human gates `waiting` on the caller across their own workflows (user-scoped, oldest first). Backs the Web-CLI `approvals` list — the same view the chat `/approvals` renders. Read-only; the decision flows through `decide_pending_approval` below.
const url = 'https://example.com/api/workflows/pending-approvals';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/workflows/pending-approvalsResponses
Section titled “Responses”GET /api/workflows/pending-approvals row — one human gate waiting on the
caller. The user-scoped approvals view the chat surfaces and the Web-CLI share:
a serializable projection of services::workflows::PendingApproval, keyed by
workflow_run_id (the id the decide-by-run endpoint takes — at most one human
node waits per run, so the run id alone resolves the gate).
object
Examplegenerated
[ { "deadline_at": "2026-04-15T12:00:00Z", "instructions": "example", "title": "example", "waiting_since": "2026-04-15T12:00:00Z", "workflow_name": "example", "workflow_run_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }]Authentication required
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Permission denied
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Structured server error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}