Telegram Channel Scraper & Monitor avatar

Telegram Channel Scraper & Monitor

Pricing

$1.00 / 1,000 results

Go to Apify Store
Telegram Channel Scraper & Monitor

Telegram Channel Scraper & Monitor

Scrape public Telegram channels anonymously — posts, views, reactions, subscriber counts and engagement stats. Channel monitoring and keyword watchlists for researchers, analysts and marketers. From $1/1,000 results.

Pricing

$1.00 / 1,000 results

Rating

0.0

(0)

Developer

William Billings

William Billings

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Extract data from public Telegram channels — no account, no Bot API key, no phone number required. Get channel stats, full post history with view counts and reactions, monitor channels for new posts, and compute engagement metrics. Built for researchers, OSINT analysts, crypto/finance trackers, media monitors, and social-listening teams.

Why this actor?

Most Telegram scrapers dump raw messages. This one is built for analysis and monitoring:

  • Channel intelligence — subscribers, media counts, description, profile
  • Post metrics — every post includes views, reactions, forwards, media type
  • Watch mode — fetch only posts new since your last run (by date or post ID) — perfect for scheduled monitoring
  • Snapshots — per-channel engagement summary (avg views, engagement rate) across any channel list — build your own TGStat
  • Anonymous & free to run — uses Telegram's public web preview, no credentials

Modes

ModeOutputUse case
channelOne row per channel: title, subscribers, media counts, descriptionChannel lookup & vetting
postsOne row per post: text, date, views, reactions, media flagsFull history export, content analysis
watchPosts published after a date or post IDScheduled monitoring & alerts
snapshotPer-channel: latest post ID, avg views, engagement rateChannel analytics, leaderboards

Input examples

Channel profile:

{ "mode": "channel", "channels": ["bitcoin", "durov"] }

Recent posts with keyword filter:

{
"mode": "posts",
"channels": ["bitcoin"],
"maxPostsPerChannel": 100,
"keyword": "etf"
}

Monitoring — only new posts since last run (schedule daily):

{ "mode": "watch", "channels": ["bitcoin"], "publishedAfter": "2026-09-28" }

or precisely:

{ "mode": "watch", "channels": ["bitcoin"], "afterPostId": 20400 }

Engagement snapshots across a list:

{ "mode": "snapshot", "channels": ["bitcoin", "ethereum", "durov", "telegram"] }

Output fields

channel records — username, title, description, subscribers, photosCount, videosCount, filesCount, photoUrl, url

post records — channel, postId, url, date (ISO), text, views, reactions [{emoji, count}], forwardedFrom, hasPhoto, hasVideo, hasDocument, hasPoll, linkPreview

snapshot records — channel fields plus latestPostId, latestPostDate, postsInSample, avgViewsLast20, maxViewsLast20, totalReactionsLast20, engagementRate (avg views ÷ subscribers, %)

All human counters (184K, 5.16K) are normalized to integers.

Tips for scheduled monitoring

  1. Run snapshot or posts once to get latestPostId per channel.
  2. Store it, then schedule watch runs with afterPostId — you only pay for new posts.
  3. Pair with a webhook/dataset-diff integration to get alerts.

Limits & caveats

  • Public channels only. Private groups/channels and member lists require authentication and are not supported.
  • The public preview serves ~20 posts per page — deep history works via pagination but each 20 posts costs a request.
  • Subscriber counts reflect the public counter (rounded by Telegram, e.g. 184K).
  • Edited/deleted posts reflect their current public state.

Pricing

$1.00 per 1,000 results (pay-per-event). A 20-post scan of one channel costs a fraction of a cent. Scheduled watchlists are nearly free.

Example output

{
"recordType": "post",
"channel": "telegram",
"postId": 441,
"url": "https://t.me/telegram/441",
"date": "2026-05-14T16:08:31+00:00",
"text": "Bot-to-Bot Communication. Bots are now able to respond to other bots, not just users.\n\nAI enthusiasts can utilize this to create custom workflows with autono...",
"views": 1510000,
"forwardedFrom": null,
"reactions": [],
"hasPhoto": false,
"hasVideo": true,
"hasDocument": false,
"hasPoll": false,
"linkPreview": []
}

FAQ

Does Telegram Scraper need a login or API key? No — every row comes from public endpoints. Provide a proxy only if your network is heavily rate-limited.

How do I monitor on a schedule? Attach the actor to an Apify Schedule (daily/weekly) and use the watch/monitor mode if present — each run emits a fresh, diff-able dataset.

What does each row contain? See the output fields table above; every row carries a scrapedAt timestamp so datasets can be deduped across runs.

Is it legal to scrape this data? The actor only accesses publicly available data — the same pages/APIs a browser sees. Scraping public data for research, monitoring, and analysis is common practice, but platform Terms of Service and the rules in your jurisdiction still apply to how you use it. Consult legal counsel for your specific case.

More from this developer

Alt-social & OSINT: Gab Scraper · BitChute Scraper · Truth Social Scraper · Rumble Video Scraper · Odysee Scraper · Kick Scraper · Discord Scraper · 4chan Scraper · Bitcointalk Scraper · Xiaohongshu / RedNote Scraper

Creator platforms: Bluesky Scraper · Threads Scraper · Farcaster Scraper · Spoutible Scraper · Pixelfed Scraper · Substack Notes Scraper · Dailymotion Scraper · Roblox Scraper

Gov & regulatory: Federal Register Monitor · Federal Court Monitor · FDA Compliance Monitor · Clinical Trials Monitor · Lobbying Monitor