Catalog

Telegram API

Telegram data through one normalized API - per-request USD pricing, no subscriptions, and automatic failover on redundant endpoints.

Endpoints3Providers3From · channel$1.10/1k req · LemurFull breakdownRead docs
Uptime
100.00%
30d · 4 calls
Requests
4
30d
Response
1.3s
median · 30d
POST

Channel

Most used
/v1/run/telegram.channeltelegram.channel
Get a public Telegram channel by username: name, bio, photo, verified badge, exact subscriber count, and how many photos, videos, files and links it has posted.
2 /mo
100.00%
1066ms p50
3
from$1.10/1k req
Lemur
POST

Channel posts

/v1/run/telegram.channel_poststelegram.channel_posts
Get a public Telegram channel's posts by username, about 20 per page with a cursor for older pages: text, posting time, views, photo and video links, and reactions.
1 /mo
100.00%
1176ms p50
3
from$1.10/1k req
Lemur
POST

Post

/v1/run/telegram.posttelegram.post
Get one public Telegram channel post by its t.me link: text, posting time, views, photo and video links, and reactions.
1 /mo
100.00%
1891ms p50
3
from$1.10/1k req
Lemur

About the Telegram API

Every provider prices each endpoint independently, so the table shows the cheapest per endpoint. Open one to compare all providers.

Measured performance

What the Telegram API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (4 calls)
Succeeded on first lane 100.0%
Response time estimate (4 calls across endpoints)
Weighted p50 estimate
1.3s
Request-weighted average of endpoint p50 values, not a combined request percentile
Weighted p99 estimate
1.5s
Request-weighted average of endpoint p99 values, not a combined request percentile

FAQ

About the Telegram API

The AnyAPI Telegram API returns Telegram data as normalized JSON across 3 endpoints: channel, channel posts, and post. You call one endpoint per job with a single key, and AnyAPI routes each request across 3 sources, falling back automatically when one fails. Pricing is in US dollars, from $1.10 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Telegram calls through AnyAPI succeeded, with a request-weighted median response time of 1.3 seconds across 4 measured calls.

Pricing is in US dollars, from $1.10 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

3 endpoints: channel, channel posts, and post. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Telegram endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Telegram calls through AnyAPI succeeded, with a request-weighted median response time of 1.3 seconds across 4 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.