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

# Call page.video_upload

`POST /api/v1/tools/page.video_upload`

## Request

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

Bring a video file of the customer's own into the workspace so a page can play it — 'upload our demo video', 'port this mp4 to the site'. Start with the file's name, type and size; the answer is one upload address, or parts to request with sign_parts and send in order; complete records the video, and abort abandons it. The video is stored and never hosted until it is attached to a page; storage is charged per month. On a key with no member behind it, start returns a confirmation_id first, and so does a complete that names captions, because captions are charged per language minute; calling the same action again with that confirmation_id runs the recorded request, and a confirmed complete stores exactly the caption languages it recorded. Not for putting the finished video on a page — that is `page.api_video_attach`.

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
  - `action` 'start' | 'sign_parts' | 'complete' | 'abort', required
  - `filename` string
  - `mime_type` string
  - `byte_size` integer
  - `upload_id` string, uuid
  - `part_numbers` integer[]
  - `parts` object[]
    - `part_number` integer, required
    - `etag` string, required
  - `title` string
  - `captions` object
    - `languages` string[], required: Caption languages as short tags, like en or pt-BR.
  - `confirmation_id` string, uuid
  - `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
    - `action` 'start' | 'sign_parts' | 'complete' | 'abort', required
    - `state` 'confirmation_required' | 'open' | 'signed' | 'stored' | 'abandoned', required
    - `confirmation_id` string, uuid
    - `expires_in_seconds` integer
    - `upload_id` string, uuid
    - `mode` 'single' | 'multipart'
    - `part_size_bytes` integer
    - `part_count` integer
    - `put_url` string
    - `part_urls` object[]
      - `part_number` integer, required
      - `put_url` string, required
    - `urls_expire_at` string
    - `video_id` string, uuid
    - `title` string, nullable
    - `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/6d82fb124064?raw)