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

# Call ads.accept_plan

`POST /api/v1/tools/ads.accept_plan`

## Request

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

Accept the plan and set up the campaign — 'looks good, go with that', 'yes, make the campaign', 'go with four ads'. Accepts the plan `ads.plan` read back for this brief: it makes the campaign and its board with the plan's ads, budget and dates, and returns the campaign_id the board's tools take. Pass concept_count whenever the person named a number of ads in this conversation, and campaign_name only when they renamed it. It draws no ads and spends nothing — drawing them is the next step, and the campaign's board starts that drawing by itself when it opens — and accepting again refreshes the same campaign rather than making a second. Not for drawing the ads — that is `ads.draft_creatives`.

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
  - `run_id` string, uuid, required: The brief's run id, as `ads.start_brief` returned it.
  - `campaign_name` string: A new name for the campaign, only when the person gives one. Leave it out to keep the plan's name.
  - `concept_count` integer: How many ads: the number the person agreed to in this conversation, whether they said it with the accept ('go with four') or on an earlier read-back ('make it two'). Leave it out only when they never named one.
  - `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
    - `campaign_id` string, required: The campaign's id — pass it to `ads.draft_creatives`.
    - `board_path` string, required: Where the board is, e.g. /ads/<id>.
    - `campaign_name` string, required
    - `concept_count` integer, required: How many ads the board will hold once they are drawn.
    - `daily_budget_cents` integer, required
    - `created` 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/6d82fb124064?raw)