Hanzo
OpenapiIntegrations

Discord sign-in return leg

Where Discord returns the user after the identify consent.

GET /v1/integrations/discord/link/discord

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

Where Discord returns the user after the identify consent. It resolves the verified Discord user, confirms the server is connected to an org, and hands the browser to the Hanzo sign-in that completes the link.

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/discord 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 discord

Integrations API · All Hanzo APIs · Interactive reference

How is this guide?

On this page