Lists the user-scoped provider cards — the catalog of what a user can connect,…
Lists the user-scoped provider cards — the catalog of what a user can connect, and how.
GET /v1/integrations/connectors/providers
| Address | https://api.hanzo.ai/v1/integrations/connectors/providers |
| Method | GET |
| Operation | get_integrations_connectors_providers |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Lists the user-scoped provider cards — the catalog of what a user can connect, and how. Methods derive from capabilities (Device/Adopt/Verify — Mount asserts at least one), never from a parallel kind enum.
Request
GET /v1/integrations/connectors/providers takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | connectorProvidersOut | ok |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
providers | body | connectorProviderView[] | — | Providers is every USER-scoped provider, sorted by id. |
providers[].category | body | string | — | Category groups the card. |
providers[].description | body | string | — | Description is the one-line pitch the console card shows. |
providers[].id | body | string | — | ID is the provider's registry id and the :provider path segment. |
providers[].methods | body | string[] | — | Methods are the intake paths this provider supports, derived from its capabilities: "device", "oauth" (adopt an externally obtained bundle) and "token" (a… |
providers[].name | body | string | — | Name is the provider's display name. |
providers[].scopes | body | string[] | — | Scopes are the permissions a connection will ask for. |
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, IntegrationsApi } from 'hanzoai';
const api = new IntegrationsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getIntegrationsConnectorsProviders();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IntegrationsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IntegrationsApi(client).get_integrations_connectors_providers()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IntegrationsAPI.GetIntegrationsConnectorsProviders(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, integrations_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = integrations_api::get_integrations_connectors_providers(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IntegrationsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IntegrationsApi(client).getIntegrationsConnectorsProviders();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/integrations/connectors/providers \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches integrations through the integrations tool, which names its 45 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_connectors"
}
}
}'How is this guide?