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

# Call work.file

`POST /api/v1/tools/work.file`

## Request

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

File or move any item — a document, photo, video, file, table, email, post, site, automation — or a whole project into a project the member names — 'move the onboarding video to the Clients project', 'put the Holiday gift boxes project under Wholesale cafes', 'the menu photos belong in Spring launch'. Any item (a site, an automation, a video or short, a post, an image or photo, a document, an uploaded file, a data table, an email, a widget) or a project, which takes everything inside it along. This verb finds the item itself, so call it on the ask: put the member's words for the thing in item_name, a generic name too ('the new doc', 'that photo from Friday'), for any item but a widget. Among several matches it takes the one in the project the member is on, then the exact name; otherwise it moves nothing and answers with the matches by name and place, so you can ask which. Read `board.tree` for to_project_id, the id of the project the member names; the tree lists projects, not the items inside them, so look for the item through this verb rather than in the tree. The project the member is on (the page's board_id) is where the item comes from, so it is never to_project_id here; putting a thing on that project is `items.place`. It leaves where it was and lives only in the new project; its shortcuts follow it, nothing is copied or deleted, and the member can undo it. A null to_project_id takes a project out to the top level of Projects; name a project being moved with item_kind project and its id from `board.tree`. Not for putting something on the project the member is on right now (`items.place`), or for showing it in a second project while it stays where it lives (`work.shortcut`).

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` 'site' | 'automation' | 'video' | 'post' | 'image' | 'document' | 'file' | 'table' | 'email' | 'widget' | 'project': What it is: a site, an automation, a video (or short), a post, an image (a photo or picture), a document, an uploaded file, a data table, an email, a widget, or a project.
  - `item_id` string, uuid: Its id, only when a verb or the page already showed it to you (a project's from `board.tree`, a widget's from `widget.list`). Otherwise send item_name: never call a list just to find an id.
  - `item_name` string: The member's words for its name, title or subject ('the latte video', 'price list', 'the Monday report automation'), a generic name included. It works for every kind but a project and a widget; the tool finds the item itself, with no read first, and when several things match the answer lists them by name and place so you can ask which.
  - `to_project_id` string, uuid, nullable, required: The project the member names as where it goes, by its id from `board.tree`. null only to take a project out to the top level of Projects.
  - `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` 'site' | 'automation' | 'video' | 'post' | 'image' | 'document' | 'file' | 'table' | 'email' | 'widget' | 'project', required
    - `item_id` string, uuid, required
    - `name` string, required
    - `from_project_id` string, uuid, nullable, required
    - `to_project_id` string, uuid, nullable, required
    - `trail` string, 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 changing 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`.

---

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