Telegram Bot API
Telegram's first-party interface for programmatic messaging. Bot API 10.3, 24 August 2026. Hunted to open growth edge 6 — the markets where a different app is the default — and it turned out to answer a bigger question than the edge asked.
How you get on the channel
Talk to BotFather, receive "a unique authentication token when it is created" (shaped like
123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11), and start calling the API. That is the entire onboarding.
Updates arrive two mutually exclusive ways: long polling via getUpdates, or a webhook set with
setWebhook, after which "we will send an HTTPS POST request to the specified URL, containing a
JSON-serialized Update." Undelivered updates are held server-side but "will not be kept longer than
24 hours." The API also carries a connected business account surface for Telegram Business.
What is missing, and it is everything this spoke calls a gate
This spoke's founding cross-channel finding is that the identity, content and intermediary gates are not WhatsApp-specific — every operator polices all three and they differ only in where enforcement lands: WhatsApp per message, Apple in a pre-launch experience review, RCS at agent launch with carriers holding a second veto.
Telegram polices none of them, on the evidence of its own API reference:
| Gate | WhatsApp / RCS / Apple | Telegram Bot API |
|---|---|---|
| Identity | brand verification, business account, carrier or Apple review | a token from BotFather |
| Content | [[message-template | templates]] pre-approved by category |
| Intermediary | BSP / partner tiers | none — you call the API directly |
| Price | per-message or per-conversation | no fee documented |
That is a counterexample to the spoke's own generalization, and it should be recorded as one rather than smoothed over. The three-gate pattern held across three operators and looked like a property of business messaging. A fourth operator has none of it. The honest revision is narrower: the gates appear where the channel is somebody's phone number — WhatsApp, RCS and Apple all ride the carrier identity system and inherit its abuse and billing controls, while Telegram issues its own identifiers and charges nothing for them. The pattern is about the substrate, not about business messaging.
What this page cannot say
Rate limits are not stated in the reference (they are documented elsewhere and were not fetched). No pricing appears for bot messaging — that is not proof none exists anywhere in Telegram's commercial products, only that the API reference names none, which is itself the contrast with WhatsApp's pricing page. Telegram Business, the paid tier the "connected business account" surface serves, was not fetched and is the obvious next pull.
Reflexive note: this hub is reached through a Telegram bot, so the corpus now documents its own transport.
Related
whatsapp-business-platform · rcs-business-messaging · apple-messages-for-business · message-template · per-message-pricing · business-solution-provider · sender-verification