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

# Call connections.business_profile_status

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

## Request

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

Check whether Google Business Profile is connected and can actually post right now — 'can we post to our Google Business Profile', 'why won't a local post go out'. Report whether this workspace's Google Business Profile is connected AND whether a local post can actually go out right now. Read this BEFORE offering to publish: a Business Profile can be perfectly connected while the Business Profile API still allows zero requests, because Google has not yet approved our platform's API access application — a wait on us, not on the operator. Never tell the operator to reconnect when that is the reason. Not for publishing the local post — that is `connections.publish_local_post`.

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
  - `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
    - `connected` boolean, required: Has this workspace granted Goosy access to its Google Business Profile? Connecting is the operator's click on the Business Profile card in Connections.
    - `connected_at` string, nullable, required
    - `api_access_approved` boolean, required: Has GOOGLE approved our platform-wide Business Profile API access application? This is OURS, not this workspace's — no amount of reconnecting changes it, and while it is false the API allows zero requests per minute.
    - `queries_per_minute` number, required: The request budget the Business Profile API currently allows us. Literally 0 before the access application is approved, 300 after.
    - `can_publish` boolean, required: True only when the workspace is connected, the access application is approved, and the execution switch is on. When false, `why_not` is the sentence to give the operator — do not paraphrase it into something more hopeful, and never offer to publish.
    - `why_not` string, nullable, 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/0e033701d3f7?raw)