Connect telegram
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/provider/telegram/connect
| Address | https://api.hanzo.ai/v1/provider/telegram/connect |
| Method | POST |
| Operation | post_provider_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/provider/telegram/connect. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_provider_telegram_connect, which answers from the running route.
Response
| Status | Body | Meaning |
|---|---|---|
200 | provider.authorizeOut | ok |
default | problem-details | refused |
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 provider telegram connectimport { Configuration, ProviderApi } from 'hanzoai';
const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderTelegramConnect();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProviderApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProviderApi(client).post_provider_telegram_connect()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.ProviderAPI.PostProviderTelegramConnect(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, provider_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = provider_api::post_provider_telegram_connect(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProviderApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new ProviderApi(client).postProviderTelegramConnect();The method above is the one at the current release of the document. [email protected] (npm) was generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/provider/telegram/connect \
-H "Authorization: Bearer $HANZO_API_KEY"MCP declares no tool for provider — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?