Returns the ONE catalog of everything a caller can connect: every first-party…
Returns the ONE catalog of everything a caller can connect: every first-party connector and every long-tail one, in a single list sorted by provider.
GET /v1/knowledge/connectors/catalog
| Address | https://api.hanzo.ai/v1/knowledge/connectors/catalog |
| Method | GET |
| Operation | get_knowledge_connectors_catalog |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the ONE catalog of everything a caller can
connect: every first-party connector and every long-tail one, in a single list
sorted by provider. configured reports whether this deployment holds OAuth
credentials for a source, so the console can show Connect rather than a dead
button, and kind is a badge only — the connect and sync lifecycle is
identical for both. The catalog itself is org-independent; a validated
principal is still required. It is metadata only: no secret is ever returned.
Request
GET /v1/knowledge/connectors/catalog takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | catalogOut | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
connectors | body | catalogEntry[] | — | Connectors is every connectable source, sorted by provider. |
connectors[].configured | body | boolean | — | Configured is whether THIS DEPLOYMENT holds the OAuth client credentials for the provider. |
connectors[].description | body | string | — | Description is one line of shop copy: what connecting this source pulls in. |
connectors[].displayName | body | string | — | DisplayName is the label to show a person. |
connectors[].kind | body | string | — | "native" | "piece" |
connectors[].provider | body | string | — | Provider is the source's id and the address every connector op takes it by (/v1/knowledge/connectors/:provider). |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, KnowledgeApi } from 'hanzoai';
const api = new KnowledgeApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getKnowledgeConnectorsCatalog();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import KnowledgeApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = KnowledgeApi(client).get_knowledge_connectors_catalog()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.KnowledgeAPI.GetKnowledgeConnectorsCatalog(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, knowledge_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = knowledge_api::get_knowledge_connectors_catalog(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.KnowledgeApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new KnowledgeApi(client).getKnowledgeConnectorsCatalog();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/knowledge/connectors/catalog \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches knowledge through the knowledge tool, which names its 9 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_kb_connectors"
}
}
}'How is this guide?