Hanzo
OpenapiIntegrations

Lists the caller's OWN connectors across every provider — the set `hanzo…

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

GET /v1/integrations/connectors

Addresshttps://api.hanzo.ai/v1/integrations/connectors
MethodGET
Operationget_integrations_connectors
AuthAuthorization: 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/integrations/connectors takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200connectorsOutok

200 body — 9 fields.

FieldInTypeAlwaysDescription
connectorsbodyconnView[]Connectors is the caller's own set.
connectors[].accountbodystringAccount is the provider's label for the connected account.
connectors[].connectedAtbodystringConnectedAt is when the connector was last (re)established, RFC 3339 UTC.
connectors[].expiresAtbodystringExpiresAt is when the access token expires, RFC 3339 UTC; empty for a non-expiring credential.
connectors[].externalIdbodystringExternalID is the provider's own id for that account.
connectors[].idbodystringID is provider + ":" + label — what every other connector route addresses.
connectors[].labelbodystringLabel is the caller's name for this connection ("default", "work").
connectors[].providerbodystringProvider is the user-scoped provider's registry id.
connectors[].scopesbodystring[]Scopes are the permissions the credential carries.

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.


Integrations API · All Hanzo APIs · Interactive reference

How is this guide?

On this page