List the connectors used by the caller's toolboxes
Lists the connectors that appear in the toolboxes GET /toolbox would return for this caller, and how many of those toolboxes hold each one. These are the options for GET /toolbox?connector_slug=, the same way GET /connector/categories is the options for GET /connector?category=. Build a connector filter on this rather than on GET /connector: the catalog offers connectors the caller has no toolbox for, and the empty list that follows selecting one reads as a bug. Filtering on any slug returned here yields exactly that row's toolbox_count toolboxes from GET /toolbox under the same ?type=, so pass ?type= here whenever you pass it there. toolbox_count counts distinct toolboxes over the caller's whole visible set, never over one page of it. Ordered most-used first, slug ascending as the tiebreak. Cursor-paginated. Visibility follows GET /toolbox: a connector reachable only through someone else's private toolbox is not listed.
Request
- Base URL: https://api.elaichi.ai
- URL: https://api.elaichi.ai/toolbox/connector
- Auth: HTTP bearer
Query parameters
Page size. Defaults to 50. Values above 200 are silently clamped to 200 rather than rejected; a value below 1, or a non-integer, is a 400. Ignored by the endpoints documented as unpaginated.
Opaque cursor — pass the next_cursor from a previous response. Ignored by unpaginated endpoints.
Prefix match on the connector slug (goo matches google-drive), not on the display name. LIKE wildcards are matched literally. Max 200 characters.
Mirrors GET /toolbox's ?type= and must be given the same value: stored counts only real, shareable toolboxes, automatic only the automatic global:…/connection:… rows, unset both. Any other value is a 400.
Headers
Target organization (org_…). Required for cookie/session auth on org-scoped routes; optional for API tokens, which carry their organization, and rejected when it names a different one.
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.