posts

Call posts.set_schedule

Set or clear the time one post piece goes out — 'schedule this post for Tuesday at 9am', 'move the launch post to Friday', 'take the time off this piece'. The time is when the piece reaches its audience on every destination without a time of its own, and nobody is asked again at that moment. A time someone changed in between is refused rather than overwritten. Not for reading the piece's current time — that is posts.api_read_piece. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

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.

post/api/v1/tools/posts.set_schedule

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/posts.set_schedule
  • Auth: HTTP bearer

Headers

x-request-idstring

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.

Request body

piece_idstring uuid required

The piece's id, as content.create_request, content.status or schedule.read return it.

scheduled_forstring date-time nullable required

When the piece goes out, ISO 8601 with a Z or an offset; null clears the time. Pass it on both calls.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

workspacestring

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

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.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.