Get connector detail

Copy page

GET /connector/{slug}

Catalog detail plus `restricted`, which reports whether the caller's restrictions block this connector — a restricted connector still resolves here but cannot be connected or executed. For an org-owned connector the response also carries its config, `can_manage`, `can_share` (mirrors `POST /:slug/share`'s own gate: edit access AND `connector:share`, never a `connector:manage` fallback), the bounded `access_summary` (same shape as connection/toolbox's — counts plus a few resolved names; page `GET /:slug/share` for the full grant list) and `shares`, present only when the caller has a real `edit` grant of their own — never for a bare `connector:manage` holder with no grant (removed 2026-09-04: org owners/admins do not see access details nobody explicitly shared with them, and there is no oversight audit trail for connectors any more). A custom connector the caller cannot see is `404`, never `403`. Platform catalog connectors need only `connector:view`.

Path Parameters

Response Body

curl -X GET 'https://api.elaichi.ai/connector/<slug>' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json'

const response = await fetch('https://api.elaichi.ai/connector/<slug>', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);

import os
import requests

url = "https://api.elaichi.ai/connector/<slug>"
headers = {
    "Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
    "Content-Type": "application/json",
}

response = requests.get(url, headers=headers)
print(response.json())