`GET /api/tool-approvals/board` — the #691 §E server-paginated pending-approvals board: filtered+paged REDACTED rows + total + (optional) kind facets.
const url = 'https://example.com/api/tool-approvals/board';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/tool-approvals/boardParameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Exact kind (tool | question | visual) — the facet/select.
Free-text search over the payload tool-name / prompt.
Whitelisted sort key: created_at | kind.
Sort direction asc | desc (default desc).
Recompute the workspace kind facets (default true).
Responses
Section titled “Responses”One page of the pending-approvals board: the REDACTED rows, the filtered total (for the pager), and — only when requested — the workspace kind facets.
object
The kind facet chips ({value,count} per pending kind, largest-first).
object
One filter-chip value and its count. Counts are workspace-wide (independent of the active filter — the chip totals do not shift as the user filters).
object
How many rows fall in this bucket.
The bucket value (e.g. a scope, a role, a framework).
A pending approval as the chat/web pending-list surfaces it — the compact,
REDACTED projection (pending_tool_approvals port / the dashboard view), so
no surface re-redacts. payload is already redacted for chat delivery.
object
Examplegenerated
{ "facets": { "kinds": [ { "count": 1, "value": "example" } ] }, "items": [ { "created_at": "2026-04-15T12:00:00Z", "deadline_at": "2026-04-15T12:00:00Z", "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "image_urls": [ "example" ], "kind": "example", "payload": "example", "task_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "timeout_policy": "example", "workspace_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" } ], "total": 1}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"}