Hanzo
OpenapiIntegrations

Mints a short, single-use deep-link code bound to the caller's org and returns…

Mints a short, single-use deep-link code bound to the caller's org and returns the t.me link the console navigates to.

POST /v1/integrations/telegram/connect

Addresshttps://api.hanzo.ai/v1/integrations/telegram/connect
MethodPOST
Operationpost_integrations_telegram_connect
AuthAuthorization: Bearer $HANZO_API_KEY

Mints a short, single-use deep-link code bound to the caller's org and returns the t.me link the console navigates to. Org-authed: a caller with no validated principal is 403 (same gate as the framework connect). The code is stored as an oauth_nonce (org,telegram); the webhook's /start handler claims it to bind chat→org. It is short (128-bit hex) so it fits Telegram's 64-char start payload limit.

Request

The document declares no body for POST /v1/integrations/telegram/connect. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_integrations_telegram_connect, which answers from the running route.

Response

StatusBodyMeaning
200authorizeOutok

200 body — 1 field.

FieldInTypeAlwaysDescription
authorizeUrlbodystringAuthorizeURL is the provider consent (or bot deep-link) URL.

Failure carries the platform error shape — see Errors.

Examples

hanzo integrations telegram connect

Integrations API · All Hanzo APIs · Interactive reference

How is this guide?

On this page