Skip to main content
POST
Call video_unit.set_destinations

Authorizations

Authorization
string
header
required

An API key minted at Settings › API & MCP. Send it as Authorization: Bearer <key>. A key carries its holder's own permissions, resolved on every call — revoking a membership closes the key's reach immediately. Keep it in an environment variable (GOOSY_API_KEY), never in a committed file.

Headers

x-request-id
string

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.

Maximum string length: 128

Body

application/json
destination_keys
string[]
required

Only the destination keys to start shipping this video to, from the keys the Ship step offers for this workspace; a key that is not available is refused with the catalog's own reason. Every destination already chosen stays.

Maximum array length: 32
no_destination
boolean
required

True only when the operator is deliberately finishing this video with NO destination; it clears every destination. Otherwise false.

video_unit_id
string<uuid>

The video unit, as a UUID. Take it from the conversation's context — never invent one. OMIT it when the person is looking at the video and means that one: the tool resolves the unit whose page the question was asked on, and refuses plainly when there is none. Never ask which video before trying that.

Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$
remove_destination_keys
string[]

Only the destination keys to stop shipping this video to. Every other destination stays.

Maximum array length: 32
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.

Minimum string length: 1

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.

The tool ran and answered.

ok
boolean
required
video_unit_id
string<uuid>
required
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$
destination_keys
string[]
required
no_destination
boolean
required
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.