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
| Address | https://api.hanzo.ai/v1/integrations/telegram/connect |
| Method | POST |
| Operation | post_integrations_telegram_connect |
| Auth | Authorization: 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
| Status | Body | Meaning |
|---|---|---|
200 | authorizeOut | ok |
200 body — 1 field.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
authorizeUrl | body | string | — | AuthorizeURL is the provider consent (or bot deep-link) URL. |
Failure carries the platform error shape — see Errors.
Examples
hanzo integrations telegram connectimport { Configuration, IntegrationsApi } from 'hanzoai';
const api = new IntegrationsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIntegrationsTelegramConnect();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IntegrationsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IntegrationsApi(client).post_integrations_telegram_connect()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IntegrationsAPI.PostIntegrationsTelegramConnect(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, integrations_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = integrations_api::post_integrations_telegram_connect(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IntegrationsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IntegrationsApi(client).postIntegrationsTelegramConnect();curl -X POST https://api.hanzo.ai/v1/integrations/telegram/connect \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches integrations through the integrations tool, which names its 45 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_connectors"
}
}
}'How is this guide?