Call page.video_upload
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.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/page.video_upload
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
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.
Changes
No recorded changes to this operation across all 4 revisions of this API.