Telegram Channel Posts Scraper avatar

Telegram Channel Posts Scraper

Pricing

from $0.30 / 1,000 posts

Go to Apify Store
Telegram Channel Posts Scraper

Telegram Channel Posts Scraper

Scrapes public Telegram channels via the t.me/s/ web preview — post text, view counts, media flags, forwards, replies and links, one row per post, no API key or login required.

Pricing

from $0.30 / 1,000 posts

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 hours ago

Last modified

Share

What is Telegram Channel Posts Scraper?

Telegram Channel Posts Scraper is an Apify Actor that reads public Telegram channel posts straight from Telegram's own public web preview at https://t.me/s/<channel> — the read-only page Telegram serves to search engines and browsers with no Telegram account required. Give it one or more channel handles (@telegram, telegram, or https://t.me/telegram) and it returns one clean row per post: full text, view count, publish time, media flags, forward origin, reply target and every link mentioned in the post. No API key, no phone-number login, no MTProto client, no proxies — just the same public page a browser loads when you visit a channel without joining it.

Why use Telegram Channel Posts Scraper?

  • Media monitoring and OSINT teams track news, government and community channels for new posts, forwards and view-count spikes without registering a Telegram app or phone number.
  • Marketing and community managers measure their own channel's posting cadence, view counts and which posts get forwarded most.
  • Researchers and journalists pull a channel's post history — including who it forwards from and what links it shares — into a dataset for analysis.
  • Crypto and trading signal watchers turn a list of public channels into a structured feed of timestamped posts, ready for a keyword or sentiment pipeline.

How to use Telegram Channel Posts Scraper

  1. Fill Channels with one or more public channel handles — bare (telegram), with @ (@telegram), or a full t.me URL — one per line.
  2. Set Max posts per channel (default 50) — the Actor pages through the channel's public preview with ?before=<id> until it collects this many posts or runs out.
  3. Leave Include post text on to get full message text and every link found inside it, or turn it off for a lighter run that only reads view counts and media flags.
  4. Choose Newest posts first (default) or oldest-first ordering, and set Max concurrency for how many channels are scraped in parallel.
  5. Click Start and export the dataset as JSON, CSV, Excel or HTML from the Output tab.

Example input

{
"channels": ["@telegram", "@durov"],
"maxPosts": 50,
"includeText": true,
"newestFirst": true
}

Example output

{
"channel": "telegram",
"channelTitle": "Telegram News",
"channelSubscribers": 9560000,
"postId": 460,
"url": "https://t.me/telegram/460",
"datetime": "2026-08-26T19:12:34+00:00",
"text": "For all the info from today's update and a look back at 13 years of Telegram features — check out our blog:\nhttps://telegram.org/blog/welcome-messages-buttons-TG-13",
"views": 1150000,
"hasPhoto": false,
"hasVideo": false,
"hasDocument": false,
"isForwarded": false,
"forwardedFrom": null,
"replyToId": null,
"links": ["https://telegram.org/blog/welcome-messages-buttons-TG-13"],
"error": null,
"scrapedAt": "2026-09-13T19:45:12.769Z"
}

Data table

Telegram Channel Posts Scraper extracts up to 17 fields per row:

FieldTypeDescription
channel, channelTitle, channelSubscribersstring, numberThe handle scraped, its display name and subscriber count (e.g. 9.56M becomes 9560000)
postId, url, datetimenumber, stringMessage id, its public t.me URL and post time (ISO 8601 UTC)
text, linksstring, arrayPost message text and every URL found inside it (null/empty when includeText is off)
viewsnumberView count, parsed from Telegram's compact 1.2K / 9.56M notation
hasPhoto, hasVideo, hasDocumentbooleanWhether the post carries an attached photo, video or file
isForwarded, forwardedFromboolean, stringWhether the post was forwarded, and the origin channel's display name
replyToIdnumberThe post id this message replies to, within the same channel
error, scrapedAtstringSet when the channel could not be read (all other fields null), and the scrape timestamp

Input parameters

ParameterTypeDefaultDescription
channelsarray["@telegram"]Channel handles, @handles or t.me URLs
maxPostsinteger50Max recent posts to collect per channel (1-1000)
includeTextbooleantrueInclude message text and links found in it
newestFirstbooleantrueSort each channel's rows newest-to-oldest
maxConcurrencyinteger3Channels scraped in parallel (1-20)

Pricing

Telegram Channel Posts Scraper uses pay-per-event pricing: $0.001 per result row, plus a negligible actor-start fee. Reading the latest 50 posts from one channel costs about five cents; ten channels at 100 posts each costs about a dollar. Set Maximum cost per run and the Actor trims the work to what the budget covers instead of overspending.

Telegram Channel Posts Scraper vs. the Telegram app

The Telegram app requires an account, a phone number and manual scrolling to review a channel's history, and it has no built-in export. This Actor reads the same public preview page Telegram already serves without login, and turns any number of channels into one flat, typed row per post — ready to schedule, filter or feed into a monitoring, sentiment or archival pipeline.

Using Telegram Channel Posts Scraper with AI agents and MCP

Telegram Channel Posts Scraper is pay-per-event with limited permissions — the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes a channels list and gets structured post rows back, ready to summarise recent activity on a channel, check for new posts since a given date, or trace where a viral message was forwarded from.

FAQ

Does this need a Telegram account, phone number or bot token? No. It reads https://t.me/s/<channel>, the public HTML preview Telegram serves to anyone — including search engines — with no login of any kind.

Why does it only work for some channels? Only channels with public content preview enabled expose t.me/s/<channel>. Private channels, groups, bots and channels that disabled the web preview return a row with error set and every other field null instead of failing the run.

How far back can it read? As far as the channel's own history goes. The Actor pages through ?before=<id> until it collects maxPosts posts or a page returns nothing new, so a large maxPosts on an old, active channel can mean many requests.

Why is channelSubscribers sometimes very round or slightly stale? Telegram's public preview shows a compact, cached count (e.g. 9.56M), not a live figure — the same number you would see visiting the page in a browser without joining.

What counts as a "link" in the output? Every href inside the post's text, including Telegram's own auto-linked mentions and post cross-references (e.g. t.me/channel/123), not just external URLs.

Is this legal to run? Yes. t.me/s/<channel> is a public, unauthenticated page Telegram itself serves for search-engine indexing and link previews; no login wall is bypassed and no private content is accessed.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, runs without proxies or a headless browser, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Found a channel layout or edge case it should handle better? Open an issue on the Issues tab.