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

# Call ads.spend_statement

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

## Request

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

Read this brand's fee-transparent ad statement for one month — 'what did we spend on ads last month?', 'show me our ad statement for August' — what they paid each ad platform directly, and what they paid us, as TWO SEPARATE FIGURES. ⚠️ Always report the two separately and NEVER add them together or quote a combined total: the split is a compliance requirement, not a formatting preference, and their ad budget never passes through us. Set produce_if_missing to build a statement for a complete past month that has none yet; that is idempotent and spends nothing. The downloadable copy lives on the Ad statements page. Not for where the account's credits went — that is `billing.usage_summary`.

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
  - `period` string, nullable: The month, as `YYYY-MM` (e.g. `2026-03`). Omit it for the most recent period this brand has a statement for. Only a COMPLETE past month can have a statement — the month in progress cannot, because its figures are still moving.
  - `produce_if_missing` boolean: Produce the statement when that period has none yet. Safe to repeat: producing the same period again reproduces the same figures rather than creating a second statement. Leave it off to simply report that no statement exists.
  - `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
    - `period` string, nullable, required
    - `period_label` string, nullable, required
    - `rows` object[], required
      - `platform` 'meta' | 'google' | 'tiktok' | 'linkedin', required
      - `platform_spend_minor` number, required
      - `our_fees_minor` number, required
      - `currency` string, required
    - `available_periods` string[], required
    - `produced` 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/f9b4aeb83edc?raw)