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

# Call brand_kit.upload_asset

`POST /api/v1/tools/brand_kit.upload_asset`

## Request

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

'upload our new logo', 'add this photo of Alex to the brand', 'put our menu PDF in the brand library' — bring one file of the member's own into this workspace's brand library, as the brand page's upload does: a logo, a picture of one of the brand's people, a document, or a reference picture. It takes three steps: action start with the kind, file name, type and exact size returns an asset_id and a short-lived put_url; PUT the file's bytes to put_url; action complete with that asset_id checks the stored file against the kind's type and size limits and puts it in the library, where it reads confirmed within seconds. A logo is also suggested as the brand's logo, and its light and dark versions are made at no charge. It works only on a member's own API key, and it spends no credits. Not for a fact that is not a file — that is `brand_kit.suggest`.

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' | 'complete', required
  - `kind` 'logo' | 'person_picture' | 'document' | 'reference'
  - `filename` string
  - `mime_type` string
  - `byte_size` integer
  - `label` string
  - `person` string
  - `asset_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' | 'complete', required
    - `state` 'open' | 'landed', required: open: send the bytes, then complete. landed: the file is in the library.
    - `asset_id` string, uuid, required
    - `kind` 'logo' | 'person_picture' | 'document' | 'reference', required
    - `put_url` string: start: where to PUT the file's bytes, with the content-type in put_headers. It is the caller's own short-lived upload address.
    - `put_headers` object
    - `expires_in_seconds` integer
    - `fact_id` string, uuid
    - `job_run_id` string, uuid: complete: the confirm's job reference, for support. The file reads confirmed in seconds; read it as read_outcome_with says.
    - `read_outcome_with` object: `brand_kit.read` with kind "asset" shows the outcome.
      - `tool` 'brand_kit.read', required
      - `kind` 'asset', required
    - `line` string, 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.
      - `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/0e033701d3f7?raw)