Telegram scraper API
The InsightSocial Telegram API has 3 endpoints, from 10 credits a call. A profile call costs 10 credits, about $0.01 on Pro, and your first 10 calls up to 100 credits each are free.
The Telegram API for public channels, as JSON: subscriber counts, descriptions and recent posts with views, per-emoji reactions and media. No bot to add and no phone-number login.
3 endpoints · from 10 credits a call · 10 free calls up to 100 credits each · no credit card
curl "https://api.insightsocial.app/v1/telegram/profile?handle=example_channel" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
What Telegram data can you get?
Public Telegram data only, returned in the same JSON envelope as every other platform.
Channel profiles
Name, description, avatar, verification and subscriber count for a public channel or group.
Channel posts
A channel's recent posts page by page, and any single post by its t.me URL, with text, publish time, view count, per-emoji reactions and media URLs.
What people build with the Telegram API
Channel monitoring
Read a channel's newest posts on a schedule and keep the ones you have not stored yet, with views and reactions at the time of reading.
Reach comparison
Compare subscriber counts and per-post views across the channels in a niche to see which ones people actually read.
Research and fact-checking
Archive public posts from news or community channels by URL, with publish times and media links, for later analysis.
Telegram API endpoints
All 3 Telegram endpoints and their price in credits. Every one has a fixed price.
| Endpoint | Credits | What it returns |
|---|---|---|
| /profile | 10 | Returns a public Telegram channel or group's profile: display name, description, avatar URL, verification status, and subscriber count. |
| /profile/posts | 10 | Returns one page of recent public posts from a Telegram channel or group, each with its text, publish time, view count, reaction breakdown, and media URLs. |
| /post | 10 | Returns one public Telegram post: text, publish time, view count, the per-emoji reaction breakdown, and direct media URLs. |
Parameters, response fields and examples for each endpoint are in the Telegram API reference.
InsightSocial vs the official Telegram API
Telegram's Bot API reads only chats a bot has been added to. MTProto, the API Telegram's own apps use, needs an api_id from my.telegram.org and a user account logged in with a phone number.
| InsightSocial API | Official Telegram API | |
|---|---|---|
| Setup | Sign in and copy a key | A bot token, or an api_id plus a phone-number account |
| Channels you have not joined | Any public channel by handle | Not through the Bot API; MTProto as a logged-in user |
| Protocol | Plain HTTPS and JSON | Bot API over HTTPS; MTProto through a client library |
| Cost per call | 10 credits | No per-call price; bound by Telegram's API terms |
The official API is the right tool for posting, messaging or managing accounts you own. This one is read-only public data.
How much does the Telegram API cost?
Telegram calls start at 10 credits. Every endpoint's price is in the table above and in the free GET /v1/endpoints catalogue, so you know the cost before you call. Pro's 10,000 monthly credits cover about 1,000 channels at 10 credits each.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Repeats and retries
A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
One balance
API calls and Chrome extension exports share the same credits. The free plan includes 500 a month.
Not writing code?
Connect InsightSocial to Claude or ChatGPT and ask for Telegram data in plain English. Same account, same credits.
Telegram API: frequently asked questions
Only one it has been added to: Telegram's Bot FAQ says bots receive messages from channels where they are a member. Reading other channels through Telegram itself means MTProto with an api_id and a user account, and Telegram observes accounts that log in through unofficial clients. /v1/telegram/profile/posts reads any public channel by handle with one key.
/v1/telegram/post takes a t.me post URL and returns the text, publish time, view count, the reaction count for each emoji and direct media URLs. /v1/telegram/profile/posts returns the same fields for a channel's recent posts, page by page.
No. Only channels and groups with a public t.me handle can be read. Private channels and invite-only groups are visible to their members only.
Every Telegram endpoint is 10 credits a call, and 2 when the answer comes from the shared cache. Calls that fail or find nothing are free.
No. There is no Telegram app, OAuth flow or review. One API key in the x-api-key header works for Telegram and the other 60 platforms.
Yes. Your first 10 calls priced at 100 credits or less are free, and the free plan includes 500 credits every month. No credit card is needed to get a key.
60 requests a minute and 10 requests in flight at once, per API key. Going over either returns a 429 with a Retry-After header, and a rejected request costs nothing. There is no daily quota: past those two limits, your credit balance is what bounds volume.
List endpoints return rows in data.items and a pagination object with next_cursor and has_more. Send next_cursor back unchanged as the cursor parameter for the next page, and stop when has_more is false. A handful of endpoints page with their own parameter instead; their reference pages name it.
No. A call that errors or finds nothing costs 0 credits. A live fetch costs the endpoint's price, or for a metered endpoint what it actually read. A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
A call fetches live unless a recent copy is in the shared cache, and every response says which with the cached field; a cached answer costs 2 credits. Add fresh=1 or send Cache-Control: no-cache to skip the cache; that call is charged at the normal price.
Collecting publicly available data is generally treated differently from accessing private data, but the answer depends on your jurisdiction, Telegram's terms and what you do with personal data afterwards. The API reads public data only. Talk to a lawyer for anything commercial.
Telegram API guides
The same key works for 60 more platforms
- TikTok scraper API
- LinkedIn scraper API
- Twitter/X scraper API
- YouTube scraper API
- Reddit scraper API
- Pinterest scraper API
- Bluesky scraper API
- Truth Social scraper API
- Snapchat scraper API
- Twitch scraper API
- Kick scraper API
- Rumble scraper API
- Kwai scraper API
- Douyin scraper API
- Xiaohongshu (RedNote) scraper API
- Quora scraper API
- TikTok Shop scraper API
- Weibo scraper API
- Zhihu scraper API
- Substack scraper API
- Nextdoor scraper API
- Amazon scraper API
- App Store scraper API
- Apple Music scraper API
- Behance scraper API
- Dailymotion scraper API
- Deezer scraper API
- DEV Community scraper API
- Discord scraper API
- Dribbble scraper API
- Fandom scraper API
- Flickr scraper API
- GitHub scraper API
- Google Ads Transparency scraper API
- Google News scraper API
- Google Trends scraper API
- Gumroad scraper API
- Hacker News scraper API
- Hugging Face scraper API
- Ko-fi scraper API
- Lemmy scraper API
- Letterboxd scraper API
- Linktree scraper API
- Lnk.Bio scraper API
- Mastodon scraper API
- Medium scraper API
- MyAnimeList scraper API
- npm scraper API
- Polymarket scraper API
- Product Hunt scraper API
- Shopify scraper API
- SoundCloud scraper API
- Spotify scraper API
- Stack Overflow scraper API
- Stan Store scraper API
- Steam scraper API
- Vimeo scraper API
- Wikipedia scraper API
- Yahoo Finance scraper API
- Yelp scraper API