Telegram Channel Scraper & API - Messages, Views, No Login
Pricing
from $0.10 / 1,000 results
Telegram Channel Scraper & API - Messages, Views, No Login
Telegram channel scraper and API, no login or API key. Input: public channel names or t.me links, optional keyword and date cutoff. Output: one row per post (text, date, views, reactions, engagement rate, media URLs, forwards, replies) plus a channel row with subscribers. $0.10 per 1,000.
Pricing
from $0.10 / 1,000 results
Rating
0.0
(0)
Developer
Giovanni Rich
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Features
Share
Telegram channel scraper (a Telegram scraper for public channels) and simple Telegram API alternative: scrape Telegram messages and posts from any public channel with no login, phone number or API key. Send channel names and get back each post's text, date, views, reactions, photos, videos, files, polls, forwards and replies, plus channel info (subscribers, description), as JSON, CSV or Excel. A built-in Telegram search finds posts by keyword inside each channel.
The scraper reads Telegram's own public web preview (t.me/s/<channel>) over plain HTTP, with no headless browser. A cloud run of the default input (100 posts plus the channel row) took 36 seconds on 2 Nov 2026, and it saves one channel-info row per channel with subscribers, description, media counters and the verified badge.
What you get
- Post content: the full text with line breaks and emoji, plus the links, hashtags and @mentions found in it.
- Engagement: view count (e.g.
18.8Mbecomes18800000), every reaction with its count (including paid ⭐ Star reactions), the total reaction count, andengagementRate(reactions as a percentage of views), so you can rank posts and vet channels without extra math. - Media: photo URLs, video URLs with thumbnails and duration, albums, voice notes and audio, round videos, stickers, file names and sizes, polls with option percentages and voter counts, locations, and link previews (title, site, description, image).
- Context: forwarded-from (channel name, username, original post), reply-to (post ID and quoted text), author signature, and whether the post was edited.
- IDs and links: post ID, post URL and the numeric Telegram channel ID.
- Channel info: title, description, subscriber count, photo/video/file/link counters, the verified badge and the avatar URL.
- Full history: the scraper pages back from the newest post to the oldest. You can stop it at a post count, at a date, or let it read the whole channel.
- In-channel search: pass a keyword to get only the matching posts, using Telegram's own search.
Sample output
Real rows from a run on 24 Sep 2026 (text shortened):
| channel | postId | date | views | reactionsTotal | mediaType | text |
|---|---|---|---|---|---|---|
| bloomberg | 3225 | 2026-09-22T03:26:17.000Z | 13400 | 173 | photo | Alibaba unveils new AI chip it says is China's most powerful... |
| bloomberg | 3224 | 2026-09-03T03:10:11.000Z | 42900 | 478 | text | EXCLUSIVE: TikTok developer ByteDance secures a $30 billion... |
| bloomberg | 3223 | 2026-09-02T10:17:56.000Z | 44200 | 340 | photo | The Nepal disaster is the latest example of how climate chan... |
Use cases
- Media monitoring and news tracking across dozens of channels
- Crypto, trading and signals research: what got posted when, and how much attention it got
- Brand and competitor monitoring, influencer and channel vetting (subscribers, views per post, engagement)
- Keyword monitoring inside channels with Telegram's own search
- Datasets for NLP, sentiment analysis and LLM training
- Archiving a channel's history, with links to every media file
Pricing
$0.10 per 1,000 results (pay per result; failed requests are never charged; lowered from $0.30 on 15 Nov 2026). A result is a post or a channel-info row. The most-used Telegram channel scrapers (free-plan prices, live Apify Store search on 16 Nov 2026) charge $1.00 per 1,000 messages plus $2.00 per 1,000 channels and a $0.005 start fee (automation-lab, 269 users in 30 days), $5.00 per 1,000 + a $0.0001 start fee (tri_angle, 132 users), $3.00 per 1,000 channels (datahamster channel search, 99 users), $0.45 + a $0.005 start fee (fetch_cat, 92 users), $0.35 per 1,000 + $0.80 per 1,000 media + a $0.01 start fee (truefetch, 95 users) or $10.00 per 1,000 posts (webfinity, 54 users). Smaller ones: memo23 $0.25 + $0.001 per run (9 users), usefulapi $0.25 + $0.002 per run (12 users), maximedupre messages $0.25 + $0.001 per run (8 users), lergassy $0.20 (14 users), monkey.d.scraping $0.20 (7 users), automation-lab channel history $0.33 + $0.005 per run (11 users). Two charge less per post: nice_dev $0.099 + $0.01 per run (7 users; dearer than this actor on any run under 1 million posts) and sync-network $0.05 (0 users). scrapingmonkey (7 users) and bovi (3 users) are free actors.
| You scrape | You pay |
|---|---|
| 100 posts | $0.01 |
| 1,000 posts | $0.10 |
| 10,000 posts | $1.00 |
| 100,000 posts | $10.00 |
Plus a $0.00005 start fee per run. The Apify free plan's $5 monthly credit covers about 50,000 posts. The prefilled input (2 channels, 20 posts each) returns about 42 rows and costs about $0.004; it took 5 seconds in a local test on 4 Nov 2026 (no proxy, so cloud time will be longer).
Why this one
- Low flat price: $0.10 per 1,000 and a $0.00005 start fee, with every field in one price, below all 6 most-used channel scrapers on 16 Nov 2026 ($0.35-$10.00 per 1,000). Among paid actors with 3+ users, only nice_dev lists a lower per-post price, and its $0.01 start fee makes it dearer on any run under 1 million posts.
- No login, phone number or Telegram API key: nothing to set up and no account at risk.
- Full engagement per post: views, every reaction with counts, forwards, replies, plus media URLs, polls and files.
- Channel info row with subscribers, description and media counters for each channel.
- Date cutoff and in-channel keyword search, so daily monitoring only pays for new or matching posts.
FAQ
Is there an official Telegram API for channel messages?
Yes, but it needs setup: Telegram's own API (MTProto) requires an api_id, an api_hash and a logged-in phone number, and the Bot API only sees chats the bot was added to. This actor needs none of that: it reads the public web preview, and you start it over the Apify API with channel names and get JSON back.
What does a typical run cost? A daily monitor of 20 channels (about 10 new posts each, plus the channel-info rows) costs about $0.022 a day, about $0.66 a month. Vetting 50 channels before an ad buy (50 posts each, plus 50 channel-info rows) costs about $0.26. A channel's full 10,000-post archive costs $1.00.
Is it legal to scrape Telegram? The scraper collects only content that channel owners have published publicly on the open web. You're responsible for how you use the data, including complying with Telegram's terms of service and with privacy laws such as GDPR for any personal data that appears in posts. This is not legal advice; if you're unsure, check with a lawyer.
Do I need a Telegram account, phone number or API ID?
No. The scraper reads the same public page you see when you open https://t.me/s/durov in a browser. Only public channels with a web preview work: private channels, invite links (t.me/+...), groups and comments are not available.
How fast is it, and how far back can it go?
A local test on 4 Nov 2026 (no proxy) read 250 posts in about 9 seconds; a cloud run of 100 posts plus the channel row took 36 seconds on 2 Nov 2026. It can go all the way to the first post: set maxPostsPerChannel: 0 to read the whole history.
Can I schedule it to get only new posts, or call it via API?
Yes. Schedule the actor with onlyPostsNewerThan: "1 day" and deduplicate on url (or channel + postId). Start runs from the Apify API, the JavaScript/Python clients, Make, Zapier, n8n or the Apify MCP server.
Which proxy should I use? How does it avoid blocks?
The default Apify Proxy works; Telegram rarely blocks the preview pages. It sends realistic desktop Chrome headers and keeps a session pool: a 401, 403 or 429 response, or a page it doesn't recognise, retires that session so the next attempt goes out on a new IP, up to 6 retries by default (maxRequestRetries).
Why did a channel return 0 posts?
Check the RUN_SUMMARY record in the key-value store. It gives a stop reason for each channel, such as "channel not found" or "web preview not available (group)".
Example inputs for common jobs
Copy one into the JSON tab of the input and adjust.
Daily monitor: only the last day's posts from a list of channels (schedule it daily; deduplicate on url):
{ "channels": ["durov", "telegram", "bloomberg"], "maxPostsPerChannel": 0, "onlyPostsNewerThan": "1 day" }
Keyword alerts inside a channel: only posts that mention a term, from the last week:
{ "channels": ["bloomberg"], "searchQuery": "bitcoin", "onlyPostsNewerThan": "7 days", "maxPostsPerChannel": 0 }
Channel vetting before you buy an ad: subscribers plus the last 50 posts' views and reactions per channel (about 51 rows per channel, $0.015):
{ "channels": ["durov", "telegram"], "maxPostsPerChannel": 50, "includeChannelInfo": true }
Full archive of one channel since a date, for NLP or an LLM dataset:
{ "channels": ["https://t.me/durov"], "maxPostsPerChannel": 0, "onlyPostsNewerThan": "2025-01-01" }
Channel info for a list of channels (subscribers, description, media counters) with just the latest post each:
{ "channels": ["durov", "telegram", "bloomberg"], "maxPostsPerChannel": 1, "includeChannelInfo": true }
How to use
- Enter one or more public channels in Channels (
durov,@durovorhttps://t.me/durov). Optionally set Max posts per channel, a date limit or a search keyword. - Click Start. The prefilled input (2 channels, 20 posts each) took 5 seconds in a local test on 4 Nov 2026; the 100-post default took 36 seconds in the cloud on 2 Nov 2026.
- Download the results as JSON, CSV or Excel from the Output tab, or call the actor from your own code through the Apify API.
Input
| Field | Default | Description |
|---|---|---|
channels | durov | Usernames or links, any form: durov, @durov, https://t.me/durov, https://t.me/s/durov |
maxPostsPerChannel | 100 | Newest posts first. 0 = the whole history |
onlyPostsNewerThan | - | A date (2026-09-01) or a relative period (7 days, 2 weeks, 3 months). The scraper stops when posts get older than this. |
searchQuery | - | Returns only the posts that match this keyword |
includeChannelInfo | true | Adds one channel row per channel |
maxConcurrency | 5 | Channels scraped in parallel (1-20) |
maxRequestRetries | 6 | Retries per failed page (0-20) |
proxyConfiguration | Apify Proxy | Datacenter proxy is enough |
Input example
{"channels": ["durov", "bloomberg", "https://t.me/telegram"],"maxPostsPerChannel": 500,"onlyPostsNewerThan": "30 days"}
Output example
Each post is one dataset item with type: "post". The example below is a real item from a run on 24 Sep 2026. The long CDN URL is shortened, and 5 of its 8 reactions are left out. The item predates engagementRate, which newer rows also carry (reactions / views x 100, rounded to 2 decimals: 1.29 for this post).
{"type": "post","channel": "bloomberg","channelId": "1488156064","channelTitle": "Bloomberg","postId": 3225,"url": "https://t.me/bloomberg/3225","date": "2026-09-22T03:26:17.000Z","timestamp": 1790047577,"edited": false,"text": "Alibaba unveils new AI chip it says is China's most powerful and targets 20 gigawatts of data center capacity by 2032. https://bloom.bg/4ydroys\n\n📷: Qilai Shen/Bloomberg","textLength": 169,"views": 13400,"viewsText": "13.4K","reactionsTotal": 173,"reactions": [{ "emoji": "🔥", "customEmojiId": null, "isPaid": false, "count": 62, "countText": "62" },{ "emoji": "❤", "customEmojiId": null, "isPaid": false, "count": 33, "countText": "33" },{ "emoji": "👏", "customEmojiId": null, "isPaid": false, "count": 27, "countText": "27" }],"mediaType": "photo","mediaUrls": ["https://cdn5.telesco.pe/file/B-Vjm-tufLB1ZSrW02mb...R7w.jpg"],"isAlbum": false,"photos": [{ "url": "https://cdn5.telesco.pe/file/B-Vjm-tufLB1ZSrW02mb...R7w.jpg", "postUrl": "https://t.me/bloomberg/3225" }],"videos": [],"roundVideos": [],"audio": [],"documents": [],"sticker": null,"poll": null,"location": null,"linkPreview": null,"links": ["https://bloom.bg/4ydroys"],"hashtags": [],"mentions": [],"forwardedFrom": null,"replyTo": null,"author": null,"unsupportedInPreview": false,"input": "bloomberg","searchQuery": null,"scrapedAt": "2026-09-24T05:15:24.280Z"}
When a post has them, the fields look like this:
"forwardedFrom": { "name": "Mash Money", "url": "https://t.me/mashmoneymash/2732", "username": "mashmoneymash", "postId": 2732 },"replyTo": { "postId": 78053, "url": "https://t.me/mash/78053", "author": "Mash", "text": "..." },"videos": [{ "url": "https://cdn4.telesco.pe/file/7451201fa5.mp4?token=...", "thumbnail": "https://cdn4.telesco.pe/file/...", "duration": "0:25", "isGif": false, "tooLargeForPreview": false }],"documents": [{ "title": "Features 1.png", "size": "3.9 MB", "postUrl": "https://t.me/designers/243?single" }],"poll": { "question": "...", "type": "Anonymous Poll", "voters": 1720, "options": [{ "text": "Yes", "percent": 42 }, { "text": "No", "percent": 34 }] }
Each channel also gets one item with type: "channel":
{"type": "channel","username": "bloomberg","title": "Bloomberg","description": "The first word in business news.","subscribers": 175000,"photos": 800,"videos": 49,"files": null,"links": 3180,"verified": true,"photoUrl": "https://cdn5.telesco.pe/file/TczlHBZov8...jpg","url": "https://t.me/bloomberg","previewUrl": "https://t.me/s/bloomberg","previewAvailable": true}
The dataset has three ready-made views: Overview (date, text, views, reactions, media), Engagement (views and reactions for each post) and Channels (the channel-info rows).
Field fill rates (local test run, September 2026: 900 posts across 6 channels)
| Field | Fill rate |
|---|---|
| postId, url, date, channelId, channelTitle | 100% |
| views | 100% |
| text | 99% (the rest are media-only posts) |
| links in text | 77% |
| media (photo / video / file / poll) | 66% |
| reactions | 62% (100% on channels that have reactions turned on; some channels switch them off) |
| linkPreview | 17% |
| author signature | 17% (only channels that sign their posts) |
| hashtags | 15% |
| edited | 14% |
| forwardedFrom / replyTo | 3% / 2% |
API example
Python (pip install apify-client):
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("rel8ble/telegram-channel-scraper").call(run_input={"channels": ["durov", "https://t.me/bloomberg"], "maxPostsPerChannel": 100})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item.get("channel"), item.get("date"), item.get("views"), (item.get("text") or "")[:80])
One HTTP call that runs the actor and returns the rows (curl):
curl -X POST "https://api.apify.com/v2/acts/rel8ble~telegram-channel-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"channels": ["durov", "https://t.me/bloomberg"], "maxPostsPerChannel": 100}'
Integrations
- Make, Zapier and n8n: start runs and pass new posts into your workflows.
- Google Sheets: export the dataset straight to a spreadsheet.
- Apify API: run the actor and fetch results over REST, or with the JavaScript and Python API clients.
- Webhooks: get a call when a run finishes.
- MCP for AI agents: through the Apify MCP server (https://mcp.apify.com), Claude, ChatGPT and Cursor agents can call this actor as a tool.
- Schedules: run it daily or hourly to track channels over time.
Limits (read before large runs)
- Only public channels that have a web preview. Private channels, invite links (
t.me/+...), groups and bots have no public post history. For groups and channels with the preview turned off, the scraper returns only the channel-info row (previewAvailable: false), and the log says why. - Comments are not included. Telegram doesn't show discussion-group replies in the web preview.
- Custom (premium) emoji reactions come back as a
customEmojiIdwith no emoji character, because Telegram shows them as images. Their counts are still correct. - Counts are rounded the way Telegram shows them, e.g.
13.4Kis saved as13400. The raw text is kept inviewsTextandcountText. - Very large videos are listed without a direct file URL, because Telegram doesn't stream them in the preview. You still get the thumbnail, the duration and a link to the post (
tooLargeForPreview: true). - Media URLs are signed CDN links that expire after a while. Download the files soon after the run if you need to keep them.
- A few service messages and deleted posts leave gaps in the post IDs. That's normal.
How it works (for developers)
t.me/s/<channel> returns server-rendered HTML with up to 20 posts per page, plus a <link rel="prev" href="?before=N"> cursor. The scraper parses each tgme_widget_message block with cheerio. It reads every field defensively, so one malformed post can never break a page. Channels run in parallel, and the pages of one channel run in order. Everything the scraper has already seen is kept in the actor state, so a migrated run resumes without creating duplicates.
Run it locally:
npm installnpm test # parser tests on saved fixturesAPIFY_LOCAL_STORAGE_DIR=./storage node src/main.js # input in storage/key_value_stores/default/INPUT.json
Need a custom scraper or a ready dataset? Hire me on Fiverr: https://www.fiverr.com/rel8ble