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

# Call cadence_template.create

`POST /api/v1/tools/cadence_template.create`

## Request

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

'set up a posting rhythm', 'we post three times a week' — create one cadence template in this workspace: the weekly rhythm the schedule plans slots from, written out slot by slot (weekday, time, destination, asset type and piece format). Nothing publishes and nothing is scheduled by it. Leave the slots out to create an empty rhythm. Not for making a rhythm the default — that is `cadence_template.set_default`.

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

## Request body

- object
  - `name` string, required: What to call the rhythm. It must be unique in the workspace — a duplicate is refused, not silently renamed.
  - `description` string: A sentence on what this rhythm is for.
  - `slots` object[]: The weekly slots, in the order they should appear. Leave it out to create an empty rhythm the operator fills in on the Cadence surface.
    - `day_of_week` integer, required: Which weekday this slot publishes on, 0 = Monday through 6 = Sunday.
    - `time_of_day` string, required: The wall-clock time this slot publishes at, HH:MM (24-hour). It is workspace-local, not UTC.
    - `destination` string, required: Where this slot publishes — the destination key.
    - `required_asset_type` string, required: What kind of asset this slot expects.
    - `piece_format` 'posts' | 'stories' | 'shorts_clips' | 'long_form' | 'articles' | 'podcast', required: What kind of content this slot publishes. Required — a slot with no format is invisible to every rhythm view, so the rhythm would run and plan nothing. Pick the one the member described: posts for a social post, stories for a story, shorts_clips for a short vertical video, long_form for a full-length video, articles for a written article, podcast for an audio episode.
    - `approval_required` boolean: Whether a person must approve before this slot publishes.
  - `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
    - `template_id` string, required
    - `name` string, required
    - `slot_count` number, required
    - `is_default` boolean, 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.
      - `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/bd8f793b36b5?raw)