`GET /api/inbox/decisions/count` — the aggregate pending-decision count (#874 IA-1a). Counting-parity with `GET /api/inbox/board` is structural: both run [`sources::fetch_all`], so a source the caller cannot read (or that errors) contributes 0 here exactly when it contributes 0 there.
const url = 'https://example.com/api/inbox/decisions/count';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/inbox/decisions/countResponses
Section titled “Responses”The decision-inbox count, total plus the per-source breakdown the total is
the sum of. The breakdown is not cosmetic: it is what makes a badge/inbox
disagreement diagnosable instead of a mystery number. Every field is the
caller’s ACTIONABLE count for that source (#976 R2: identical to the union
board’s facets.actionable arithmetic).
object
Governor profile-version proposals still open (workspace OWNER only).
Memory-governance review items still pending (admin + entitlement).
Sum of the source counts — equals the board’s facets.actionable.
AI-scaffold proposals still pending (member-decidable). #976 R2.
Induced-skill proposals still open (admin-decidable; 0 for a member).
Active governor recommendations (admin-decidable; 0 for a member). #976 R2.
Interactive task tool/question/visual gates (workspace-scoped).
Workflow human gates waiting on the caller (deduped per workflow run).
Examplegenerated
{ "governor_proposals": 1, "memory_reviews": 1, "pending": 1, "proposals": 1, "skill_proposals": 1, "suggestions": 1, "tool_approvals": 1, "workflow_gates": 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"}