본문으로 건너뛰기

커넥터

데이터 연결에 사용하는 커넥터 정의와 실행 구성을 관리하는 API입니다.

📄️ Test Connector Connection

Instantiate a connector with runtime-only credentials and report connectivity. The result is a list of stages: `connect`, then `probe` for a db driver that declares `PROBE_SQL`. Any failed stage fails the test. A failure the request itself caused (bad credentials, an option the driver rejects) is an HTTP error carrying the structured cause (D-E5); a failure of the environment (host down, timeout) is a 200 whose `connect` stage failed — the request was well-formed, the target was not there.

📄️ List Connector Usages

Covers MCP tools (by ``options.mcp.connector_id`` or collection-scoped ``ref``), data syncs (``source``/``target.connector_id``) and semantic tables (``connector`` name, resolved the way the query runtime resolves it). The MCP tool test is the one the delete guard uses, so the listing and the 409 agree. Pipeline and code ``@use_connector`` references live in script text and are not scanned — ``covers`` says so, and an empty listing is not proof the connector is unused. Requires read permission on the connector; the referencing resources' permissions are not checked (usage visibility intent, mirroring ``GET /datasets/{id}/usages`` and ``GET /codes/{id}/usages``). Builtins go through the same ``read`` check as ``GET /connectors/{id}``.