List token

Hands the custodied access token to its owner — the ONE place custody exits.

GET /v1/connection/{id}/token

Addresshttps://api.hanzo.ai/v1/connection/{id}/token
MethodGET
Operationget_connection_by_id_token
AuthAuthorization: Bearer $HANZO_API_KEY

Hands the custodied access token to its owner — the ONE place custody exits. The (org,user)-keyed row IS the same-user gate: another user's id is simply "no row" → 404. fresh() auto-rotates within the refreshSkew window; static providers degenerate to a plain kmsGet of Secrets[0]. Refresh tokens are NEVER returned — custody keeps the sink. The token is never logged.

Request

1 field.

FieldInTypeRequiredDescription
idpathstringyesID is the connector id, provider + ":" + label ("openai:default") — the auth-profile-id shape.

Response

StatusBodyMeaning
200provider.tokenOutok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
expiresAtbodystring—ExpiresAt is when this token expires, RFC 3339 UTC; empty if non-expiring.
labelbodystring—Label is the connector's label.
providerbodystring—Provider is the connector's provider id.
tokenbodystring—Token is the access token, rotated first if it was within the refresh window.

Failure carries the platform error shape — see Errors.

Examples

hanzo connection token <id>
import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getConnectionByIdToken({ id: 'id' });
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_by_id_token(id='id')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProviderAPI.GetConnectionByIdToken(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_by_id_token(&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).getConnectionByIdToken();
curl https://api.hanzo.ai/v1/connection/<id>/token \
  -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?