Telegram reference

Every Telegram operation, from the registry

3 operations wired in the registry, 3 of them proven by real traffic.

Choose a Telegram operation

Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.

Accounts and audiences

Telegram channel — A public channel: name, description, avatar, verification, subscriber and member counts, and photo, video and link counts.

Posts and media

Telegram channel posts — A channel's posts, one page at a time, with text, time, views, reactions and forwards, plus the channel summary.
Telegram post — One channel post: text, time, views, reactions, forward origin and media count.

Check fields and collection limits

Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.

Agents can use get_endpoint for the current contract and get_docs with topic platforms/telegram to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.

Operations

Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.

live · proven: a real upstream response has been served through this API and recorded
wired · unproven: a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
sample · free: no live upstream — /v1 refuses it, /sandbox returns a marked sample

3 operations

Elsewhere

The same registry, other shapes

Telegram overview — supported data categories and use cases for this platform.
Full endpoint reference — every platform on one page.
/openapi.json or /openapi.yaml — the machine-readable contract, for Postman, Insomnia or a client generator.
GET /v1/utility/endpoints?platform=telegram — the same rows to your code at runtime, for 0 credits.