Hanzo
OpenapiIntegrations

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

Addresshttps://api.hanzo.ai/v1/integrations/connectors/providers
MethodGET
Operationget_integrations_connectors_providers
AuthAuthorization: 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

StatusBodyMeaning
200connectorProvidersOutok

200 body — 7 fields.

FieldInTypeAlwaysDescription
providersbodyconnectorProviderView[]Providers is every USER-scoped provider, sorted by id.
providers[].categorybodystringCategory groups the card.
providers[].descriptionbodystringDescription is the one-line pitch the console card shows.
providers[].idbodystringID is the provider's registry id and the :provider path segment.
providers[].methodsbodystring[]Methods are the intake paths this provider supports, derived from its capabilities: "device", "oauth" (adopt an externally obtained bundle) and "token" (a…
providers[].namebodystringName is the provider's display name.
providers[].scopesbodystring[]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.


Integrations API · All Hanzo APIs · Interactive reference

How is this guide?

On this page