connections

Call connections.recheck_accounts

Re-check which accounts a connection can post to, and record what the provider answers — 'my page isn't showing up as somewhere to post', 'I just connected Instagram, why can't I pick it?', 'check my accounts again'. Re-read one connection for the accounts this brand can post to, and record them. Use it when the operator says a connected account is not showing up as somewhere to post, or right after they connect one. It only asks the provider: nothing is published, no setting changes, no credential is read or returned — and it never picks WHICH account is this brand's, it reports when that question is open. Not for whether a connection works at all — that is connections.health_check.

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.

post/api/v1/tools/connections.recheck_accounts

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/connections.recheck_accounts
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

connection_idstring required

The connection whose postable accounts to re-read, copied VERBATIM from a connection_ids entry returned by connections.status — call it first; the id is not derivable from a connector's name. When that card lists more than one id, ask which connection they mean rather than picking.

workspacestring

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

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.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.