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

# Call item.restore

`POST /api/v1/tools/item.restore`

## Request

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

Bring an image, a document, an email, a post, a data table, a video or short, or a widget back out of the Trash — 'bring back the lighthouse photo I trashed', 'restore the onboarding checklist doc', 'undo binning the renewal reminder email', 'I need the vendor contacts table back', 'take the open mic post out of the Trash', 'get the deleted harbor tour video back', 'put the bookings chart back'. The item returns to every project and list it left, under its name and with everything it held; nothing is charged, sent or published. A post comes back unscheduled: its place on the schedule was freed when it was trashed, so the member schedules it again. A widget comes back onto every desk and project it showed on. Call it straight away on the ask. Send `item_id` when a verb or the Trash page showed you the item's id (a widget's from `widget.list` with in_trash); otherwise send `name`, the member's words for its name, title or subject — when several trashed items match, the answer lists them so you can ask which. Not for a project — that is `board.restore` — nor a site or an automation, which comes back from the Trash page with its board.

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
- `Idempotency-Key` string, required

## Request body

- object
  - `item_kind` 'image' | 'document' | 'email' | 'post' | 'table' | 'video' | 'widget', required: What the item is: an image, a document, an email, a post, a data table, a video (a short is a video too), or a widget.
  - `item_id` string, uuid: The item's id, as a UUID a verb or the page showed you; for an automation, its definition_id; for a widget, its id from `widget.list`. Leave it out when you only have the member's words for it.
  - `name` string: The member's words for the trashed item's name, when there is no item_id.
  - `idempotency_key` string: Deprecated on REST: send the `Idempotency-Key` header instead. Still accepted until 2026-12-31; if both are sent they must match.
  - `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
    - `item_kind` 'image' | 'document' | 'email' | 'post' | 'table' | 'video' | 'widget', required
    - `item_id` string, uuid, required
    - `name` string, required
    - `restored` true, required
    - `answer_note` string, required
    - `replayed` boolean, required: True when this is the first result of an earlier call with the same idempotency_key, returned without restoring anything again.
    - `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`.

## Changes

- **2026-10-20** `f9b4aeb83edc`: 2 warning, 2 info
  - added the new `video` enum value to the `oneOf[subschema #1]/item_kind` response property for the response status `200`
  - added the new `widget` enum value to the `oneOf[subschema #1]/item_kind` response property for the response status `200`
  - added the new `video` enum value to the request property `item_kind`
  - added the new `widget` enum value to the request property `item_kind`

[Operation history](https://skmtc.dev/goosybear/apis/goosy-bear-api/changes/api/v1/tools/item.restore/post.md)

---

[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/6d82fb124064?raw)