Skip to main content
POST
Call taste_note.add

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
scope
enum<string>
required

What the note is about — 'general' when it is about the brand's work as a whole.

Available options:
general,
script,
vsl_script,
title,
description,
thumbnail
sentiment
enum<string>
required

Whether this worked, did not work, or could be better.

Available options:
worked,
didnt_work,
could_be_better
note
string
required

The note in the OPERATOR'S OWN WORDS. A taste note is frozen once written and shapes every later generation, so never paraphrase and never invent one — write what they said.

Required string length: 1 - 2000
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
written
number
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.