Connectors returns the connector catalogue.
Connectors returns the connector catalogue.
GET /v1/auto/connectors
| Address | https://api.hanzo.ai/v1/auto/connectors |
| Method | GET |
| Operation | get_auto_connectors |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Connectors returns the connector catalogue. Each entry is an external service a flow step can invoke, carrying its auth descriptor and the input properties of its actions and triggers. The catalogue is the same for every tenant, so the gate is a validated principal rather than a per-org view.
Request
GET /v1/auto/connectors takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | Catalog | ok |
200 body — 32 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
connectorCount | body | integer | — | |
connectors | body | ConnectorMetadata[] | — | |
connectors[].actions | body | ConnectorAction[] | — | |
connectors[].actions[].description | body | string | — | |
connectors[].actions[].displayName | body | string | — | |
connectors[].actions[].name | body | string | — | |
connectors[].actions[].props | body | PropSpec[] | — | |
connectors[].actions[].props[].description | body | string | — | |
connectors[].actions[].props[].displayName | body | string | — | |
connectors[].actions[].props[].name | body | string | — | |
connectors[].actions[].props[].required | body | boolean | — | |
connectors[].actions[].props[].type | body | string | — | string|number|boolean|object|array |
connectors[].auth | body | ConnectorAuth | — | |
connectors[].auth.required | body | boolean | — | |
connectors[].auth.type | body | string | — | |
connectors[].categories | body | string[] | — | |
connectors[].description | body | string | — | |
connectors[].displayName | body | string | — | |
connectors[].logoUrl | body | string | — | |
connectors[].name | body | string | — | |
connectors[].triggers | body | ConnectorTrigger[] | — | |
connectors[].triggers[].description | body | string | — | |
connectors[].triggers[].displayName | body | string | — | |
connectors[].triggers[].name | body | string | — | |
connectors[].triggers[].props | body | PropSpec[] | — | |
connectors[].triggers[].props[].description | body | string | — | |
connectors[].triggers[].props[].displayName | body | string | — | |
connectors[].triggers[].props[].name | body | string | — | |
connectors[].triggers[].props[].required | body | boolean | — | |
connectors[].triggers[].props[].type | body | string | — | string|number|boolean|object|array |
connectors[].triggers[].strategy | body | string | — | |
connectors[].version | body | string | — |
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, AutoApi } from 'hanzoai';
const api = new AutoApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getAutoConnectors();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import AutoApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AutoApi(client).get_auto_connectors()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.AutoAPI.GetAutoConnectors(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, auto_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = auto_api::get_auto_connectors(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.AutoApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new AutoApi(client).getAutoConnectors();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/auto/connectors \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches auto through the auto tool, which names its 11 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_auto_flows"
}
}
}'How is this guide?