List connection

Lists the caller's OWN connectors across every provider — the set hanzo connector ls prints.

GET /v1/connection

Provider → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/connection`
Method	`GET`
Operation	`get_connection`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the caller's OWN connectors across every provider — the set hanzo connector ls prints. Rows are keyed (org,user), so this can never surface another user's connector, and no secret is in the view.

Request

GET /v1/connection takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	provider.connectionsOut	ok
`default`	problem-details	refused

200 body — 9 fields.

Field	In	Type	Always	Description
`connections`	body	provider.connectionView[]	—	Connectors is the caller's own set.
`connections[].account`	body	string	—	Account is the human label of the connected third-party account (the Slack team name, the GitHub org login).
`connections[].connectedAt`	body	string	—	ConnectedAt is when the connection was last (re)established, RFC 3339 UTC.
`connections[].expiresAt`	body	string	—	ExpiresAt is when the access token expires, RFC 3339 UTC; empty for a credential that does not expire.
`connections[].externalId`	body	string	—	ExternalID is the provider's own id for the account (Slack team.id, GitHub installation_id) — the value inbound webhooks are mapped back to this org by.
`connections[].id`	body	string	—	ID is provider + ":" + label, the address every connection route takes.
`connections[].label`	body	string	—	Label is the caller's own name for this connection ("default", "work").
`connections[].provider`	body	string	—	Provider is the connected provider's registry id.
`connections[].scopes`	body	string[]	—	Scopes are the permissions the provider granted.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo connection list

.ts

.py

.go

.rs

.java

import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getConnection();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProviderApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProviderApi(client).get_connection()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProviderAPI.GetConnection(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, provider_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = provider_api::get_connection(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProviderApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ProviderApi(client).getConnection();

curl https://api.hanzo.ai/v1/connection \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches provider through the provider tool, which names its 38 operations with its own verbs — this one among them, under a name only MCP 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_connections"
         }
       }
     }'

Provider API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList providers NextList callback — GET /v1/provider/{provider}/callback