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

# Call connections.ad_account_status

`POST /api/v1/tools/connections.ad_account_status`

## Request

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

Check where a brand's guided ad-account setup stands — 'where are we with connecting our ad account', 'what's the status of our facebook ads setup'. Read where this brand's guided ad-account setup stands for one platform, and which step is next. Call this before answering anything about ad-account access or advertising setup — never guess the state. Read `grant_state` carefully: `awaiting_platform_access` means WE are waiting on the platform to approve our access, so the customer has nothing to do and nothing is wrong with their account; `active` is the only state that means we can manage their campaigns. Not for whether the advertising authorization is signed — that is `connections.agency_authorization_status`.

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
  - `platform` 'meta' | 'google' | 'tiktok' | 'linkedin', required: Which advertising platform's ad account to set up on that platform's own account — the customer owns the account and grants us access to it. The allowed values are the enum's; do not offer a platform outside it.
  - `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
    - `platform` 'meta' | 'google' | 'tiktok' | 'linkedin', required
    - `grant_state` 'not_started' | 'awaiting_customer_creation' | 'awaiting_authorization' | 'awaiting_platform_access' | 'request_issued' | 'awaiting_customer_accept' | 'active' | 'revoked' | 'failed', required
    - `status_sentence` string, nullable, required
    - `external_account_id` string, nullable, required
    - `next_step_key` string, nullable, required
    - `next_step_title` string, nullable, required
    - `steps` object[], required
      - `step_key` string, required
      - `title` string, required
      - `state` 'pending' | 'done' | 'skipped', 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)