connections

Call connections.health_check

Re-check one connection right now — 'is this connection still working', 'check if this fixed itself'. Re-probe one connection and report what the provider answered right now. Use it when the operator says something has stopped working, or to confirm a fix — connections.status reports the LAST recorded result, this one asks again. It only asks: nothing is published, no setting changes, and no credential is read or returned. Not for the whole list of connections — that is connections.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.

post/api/v1/tools/connections.health_check

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/connections.health_check
  • 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 to re-probe, 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, or the operator's wording fits more than one card, 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 7 revisions of this API.