`GET /api/tool-approvals/pending` — the interactive approvals `pending` across the caller's active workspace (the `X-Workspace-Id` header, else the default joined workspace), newest first, REDACTED for delivery. Read-only; the decision flows through `decide` below. The service authz's the caller's membership of the resolved workspace.

GET

/api/tool-approvals/pending

curl --request GET \
  --url https://example.com/api/tool-approvals/pending

Responses

200

Media typeapplication/json

Array<object>

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

agent_type

#712 UX-3 — the agent (harness) type of the owning task (e.g. claude). None when the task was deleted.

string | null

created_at

required

string format: date-time

deadline_at

string | null format: date-time

id

required

string format: uuid

image_urls

required

Array<string>

kind

required

string

payload

required

project_name

#712 UX-3 — the owning task’s project name. None when the task has no project or it was deleted.

string | null

task_id

required

string format: uuid

task_title

#712 UX-3 — the owning task’s title, so the Freigaben inbox row shows WHICH piece of work is asking (the id alone is an 8-hex prefix). None when the task was since deleted (LEFT JOIN). Non-sensitive identifier; not redacted.

string | null

timeout_policy

required

string

workspace_id

required

string format: uuid

Example^generated

[
  {
    "agent_type": "example",
    "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",
    "project_name": "example",
    "task_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
    "task_title": "example",
    "timeout_policy": "example",
    "workspace_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"
  }
]

401

Authentication required

Media typeapplication/json

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

code

required

Machine-readable, stable error code.

string

Allowed values: not_found unauthorized forbidden bad_request unprocessable precondition_failed conflict method_not_allowed rate_limited too_many_requests quota_exceeded database_error docker_error vault_error internal_error

details

One of:

null

null

object

Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.

object

key

required

The entitlement feature key that was hit, e.g. apps.max_count.

string

limit

required

The plan’s limit for this key.

integer format: int64

upgrade_url

required

Where to send the user to upgrade.

string

used

required

Current usage (count or bytes, per the key).

integer format: int64

error

required

Human-readable message (the server’s English text; the client may localize by code).

string

Example

{
  "code": "not_found"
}

403

Permission denied

Media typeapplication/json

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

code

required

Machine-readable, stable error code.

string

Allowed values: not_found unauthorized forbidden bad_request unprocessable precondition_failed conflict method_not_allowed rate_limited too_many_requests quota_exceeded database_error docker_error vault_error internal_error

details

One of:

null

null

object

Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.

object

key

required

The entitlement feature key that was hit, e.g. apps.max_count.

string

limit

required

The plan’s limit for this key.

integer format: int64

upgrade_url

required

Where to send the user to upgrade.

string

used

required

Current usage (count or bytes, per the key).

integer format: int64

error

required

Human-readable message (the server’s English text; the client may localize by code).

string

Example

{
  "code": "not_found"
}

500

Structured server error

Media typeapplication/json

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

code

required

Machine-readable, stable error code.

string

Allowed values: not_found unauthorized forbidden bad_request unprocessable precondition_failed conflict method_not_allowed rate_limited too_many_requests quota_exceeded database_error docker_error vault_error internal_error

details

One of:

null

null

object

Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.

object

key

required

The entitlement feature key that was hit, e.g. apps.max_count.

string

limit

required

The plan’s limit for this key.

integer format: int64

upgrade_url

required

Where to send the user to upgrade.

string

used

required

Current usage (count or bytes, per the key).

integer format: int64

error

required

Human-readable message (the server’s English text; the client may localize by code).

string

Example

{
  "code": "not_found"
}