Skip to main content
POST
Call content.create_request

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

What kind of piece to create a request for.

Available options:
posts,
stories,
shorts_clips,
long_form
day
string
required

The day it is planned for, as YYYY-MM-DD. The workspace's own cadence decides the time of day.

Pattern: ^\d{4}-\d{2}-\d{2}$
title
string

A working title. Omit to leave it untitled.

Required string length: 1 - 200
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
piece_id
string
required
format
enum<string>
required
Available options:
posts,
stories,
shorts_clips,
long_form
scheduled_for
string | null
required

When it is planned to publish, ISO 8601 UTC.

week_block_id
string | null
required

The publication week it grouped under, when the workspace has one open.

filled_planned_slot
boolean
required

True when it filled a slot the workspace's cadence already planned.

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.