Skip to main content
POST
Call content.status

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.

Body

application/json
status
enum<string>

Only pieces in this lifecycle state.

Available options:
draft,
variants_in_progress,
ready,
approved,
scheduled,
publishing,
published,
verified,
failed
format
enum<string>

Only pieces of this format.

Available options:
posts,
stories,
shorts_clips,
long_form
limit
integer
default:25

How many pieces to return, newest-updated first.

Required range: 1 <= x <= 100
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
counts
object
required

How many of the returned pieces sit in each status.

total
number
required
truncated
boolean
required

True when more pieces matched than were returned.

pieces
object[]
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.