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

# Call connections.resync_custom_connector

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

## Request

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

Re-read one of this workspace's own connectors' tool list right now — 'refresh our custom connector', 'why aren't the new tools showing up'. Re-read one of this workspace's own registered connectors' tool list, right now. Use it when the operator says they have added or changed something on their own MCP server or API and the new operations are not showing up — this asks the connector again, where the connector card reports the LAST sync. It changes no setting, reads no credential and cannot remove the connector. Read `read_ok` first: a failed read leaves the connector exactly as it was and must never be reported as a refresh. Not for checking a new address before it is set up — that is `connections.probe_connector_address`.

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
  - `connector_name` string, required: The connector's own name — the namespace segment its tools arrive under, so `docs_search` in `connector.docs_search.search`. It is matched against this workspace's own connectors; a name that matches none refuses rather than re-syncing something else.
  - `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
    - `connector_name` string, required
    - `read_ok` boolean, required: `true` — the manifest was read and the tool list below is what the connector publishes right now. `false` — the read FAILED and NOTHING was re-stamped; the connector still exists with the tools it had. Never report a failed read as a refresh.
    - `error_code` string, nullable, required: The rail's typed reason when `read_ok` is false — never a credential, never an address. `null` on success.
    - `tools_observed` integer, required
    - `tools_updated` integer, required
    - `tools_now_missing` integer, required: Tools this connector used to publish and no longer does. They stay listed on the connector's card and stop being callable; say so rather than reporting them as removed.
    - `tools_not_yet_screened` integer, required: Tools the safety screen's budget did not reach this pass. They are NOT callable yet and the next sync screens them — tell the operator to try again shortly rather than that the connector is broken.
    - `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)