Hanzo
OpenapiIntegrations

Begin linking a Hanzo account from Discord

The entry point behind the connect prompt Hanzo shows in a Discord server.

GET /v1/integrations/discord/link

Addresshttps://api.hanzo.ai/v1/integrations/discord/link
MethodGET
Operationget_integrations_discord_link
AuthAuthorization: Bearer $HANZO_API_KEY

The entry point behind the connect prompt Hanzo shows in a Discord server. It starts a link session and redirects to Discord's OAuth identify consent — the narrowest scope that establishes which Discord user is asking, and nothing more.

This is one leg of a three-leg flow, and the legs are not interchangeable: a browser is expected to arrive here only from the leg before it. The link URL's state proves the prompt was server-minted and carries the CHAT it started from — it is provenance only, and it never decides which account gets linked. The account identity always comes from the platform's own verified sign-in and a host-bound cookie, so forwarding a link to someone else cannot bind their account, and a session lifted into another browser is refused rather than completed. Each link is single-use, and a deployment without linking configured answers 503.

Request

GET /v1/integrations/discord/link takes no parameters and no body — the credential is the whole request.

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 integrations discord link get

Integrations API · All Hanzo APIs · Interactive reference

How is this guide?

On this page