connections

Call connections.read_history

Read a connected account's last 90 days so Goosy learns how this brand writes there — 'learn how we write on LinkedIn', 'read our last posts so you get our voice'. It starts a background read and returns immediately — report the status EXACTLY as returned and never claim the profile is ready. It learns MESSAGING only, never the look, and it publishes nothing. Not for re-checking which accounts a connection can post to — that is connections.recheck_accounts.

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.read_history

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/connections.read_history
  • 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

platformstring required

Which connected account to read — instagram, facebook or linkedin. Never a platform the brand has not connected.

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.