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

# Call posts.create_pieces

`POST /api/v1/tools/posts.create_pieces`

## Request

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

Create every post a brief calls for, in one call — 'make this week's posts from Tuesday's episode', 'create three posts for the launch'. Each piece is created with whatever the request already settles — what it is built from, where it goes, its own copy, its time — and gets its board, so a complete request needs no further calls beyond each destination's version. Read posts.plan_context first so slot ids, library ids and destination names are real. It creates drafts only: nothing is published or sent for approval. Not for reading where one piece stands afterwards — that is `posts.api_read_piece`.

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
- `Idempotency-Key` string, required

## Request body

- object
  - `pieces` object[], required: Every piece the brief asks for, in ONE call. A week of posts is one call, not one call per post.
    - `title` string, required: What the operator would call this piece. Short and human — it labels the tile on their grid.
    - `piece_format` 'posts' | 'stories' | 'shorts_clips' | 'long_form' | 'articles' | 'podcast', nullable: Omit for `posts`.
    - `schedule_slot_id` string, nullable: The open cadence slot from posts.plan_context this piece fills. The slot supplies the destinations AND the time, so passing it means you do not pass `platforms` or `scheduled_for` at all. Omit it for a piece the cadence has no slot for.
    - `platforms` string[], nullable: Where this piece publishes. Omit when `schedule_slot_id` is set — the slot's own defaults are the operator's rhythm and restating them is what drifts. Pass ONLY values posts.plan_context listed as electable; anything else is refused.
    - `master_content` string, nullable: The piece's own copy — the canonical version every destination's variant is shaped from. Write it here when the brief gives you enough to; otherwise omit and fill it later with posts.fill_step.
    - `source_kind` 'video_unit' | 'image' | 'document' | 'scratch', nullable: What this piece is built from. Use `video_unit` with the id from posts.plan_context's finals list when the brief names an episode. `scratch` (the default) means written in the flow and takes NO source_ref.
    - `source_ref` string, nullable: The id of the final named by `source_kind`. Required for every kind but `scratch`, and forbidden for `scratch`.
    - `scheduled_for` string, nullable: When this piece goes out: the operator's LOCAL date and time as `YYYY-MM-DDTHH:MM`, with no offset and no `Z` — the date from the `calendar` posts.plan_context returned, the time as they said it. The server converts it in `displayTimeZone`, so never convert it or add an offset yourself. Omit when `schedule_slot_id` is set. Pass it whenever the operator named a day or time, and never leave a named time out.
  - `idempotency_key` string: Deprecated on REST: send the `Idempotency-Key` header instead. Still accepted until 2026-12-31; if both are sent they must match.
  - `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
    - `created` object[], required
      - `index` integer, required: The piece's position in the request, from 0.
      - `piece_id` string, required
      - `run_id` string, required: The piece's workflow run.
    - `refused` object[], required
      - `index` integer, required
      - `code` string, required
      - `message` string, required
    - `replayed` boolean, required: True when this is the first result of an earlier call with the same idempotency_key, returned without running anything again.
    - `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/6d82fb124064?raw)