---
title: "Call approvals.list_queue"
method: POST
path: "/api/v1/tools/approvals.list_queue"
tags: ["approvals"]
---

# Call approvals.list_queue

`POST /api/v1/tools/approvals.list_queue`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/approvals.list_queue`
- Auth: HTTP bearer

List the work waiting on a human right now — 'what's waiting on me?', 'what needs approving?', 'is anything on my desk?' — rendered and in-review assets, what each one belongs to, and whose desk it is parked on ('you' or 'client'). It is the first read on a daily or weekly check-in, since what waits on them comes before anything else. Each row also carries its videoUnitId and contentBlockId, which is where approvals.request_review's subjectId comes from. Read-only. You can read what is waiting, get an item ready, and ASK a person to decide. You can never approve, reject, or decide anything yourself — say who it is waiting on and stop there. Not for one waiting item in full — that is `approvals.get_item`.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `assetType` string, nullable: Optional: narrow to one kind of asset (for example 'video' or 'thumbnail'). Leave it out to see everything waiting.
  - `limit` integer: How many waiting assets to return, most urgent first. Default 8, maximum 100.
  - `cursor` string: Where to continue: pass the `next_cursor` from the previous page, with the same filters. Omit it for the first page.
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `items` object[], required
      - `assetId` string, required
      - `assetType` string, required
      - `status` string, required
      - `videoUnitTitle` string, nullable, required
      - `videoUnitId` string, nullable, required
      - `contentBlockId` string, required
      - `isPrimary` boolean, required
      - `waitingOn` string, required
      - `updatedAt` string, required
    - `count` number, required
    - `next_cursor` string: Present when there is another page: pass it back as `cursor` to read it. Absent on the last page.
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/f9b4aeb83edc?raw)