Hanzo
OpenapiAi

Completes OAuth: the org is recovered from the SIGNED state (not a header), the…

Completes OAuth: the org is recovered from the SIGNED state (not a header), the code is exchanged for a token, the token is SEALED into KMS (never the…

GET /v1/ai/connections/{provider}/callback

Addresshttps://api.hanzo.ai/v1/ai/connections/{provider}/callback
MethodGET
Operationget_ai_connections_by_provider_callback
AuthAuthorization: Bearer $HANZO_API_KEY

Completes OAuth: the org is recovered from the SIGNED state (not a header), the code is exchanged for a token, the token is SEALED into KMS (never the row/logs) through the same path as a BYOK key, and the org's provider row is upserted to "connected". The browser is then redirected back to the console with ?ai_connected=<provider> (or ?ai_connect_error=<provider> on failure). Because the org comes from the state THIS server signed, an attacker cannot land their token in a victim org — which is why this endpoint is state-authenticated rather than credential-gated.

Request

1 field.

FieldInTypeRequiredDescription
providerpathstringyes

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo ai connections callback <provider>

AI API · All Hanzo APIs · Interactive reference

How is this guide?

On this page