Telegram Post Detail Scraper avatar

Telegram Post Detail Scraper

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Telegram Post Detail Scraper

Telegram Post Detail Scraper

Fetch a single Telegram public-channel message by t.me URL or '<channel>/<id>' shorthand. Returns text, media, views, reactions, forward, reply.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

Farhan Febrian Nauval

Farhan Febrian Nauval

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

7 days ago

Last modified

Features

Limited permissions

Share

Fetch a single public Telegram channel message by URL — text, media, views, reactions, author, and reply context — without a Bot API token, login, or phone number.

Why use this actor

  • No account / no login required — just paste a t.me/<channel>/<id> URL or shorthand.
  • No Bot API token needed — works with the same public preview Telegram serves to anonymous web visitors.
  • One URL in, one record out — perfect for citation, fact-check, permalink archival, and moderation workflows.
  • Bulk-friendly — feed an array of URLs and process many posts in a single run.
  • Rich detail — message text, photo and video URLs, views, reactions, author, forwarded-from source, and reply-to context.
  • Stable JSON output suitable for pipelines, spreadsheets, and databases — every row carries _input, _source, _scrapedAt envelope fields so you can join results back to your input list.

How it works

  1. You provide a list of Telegram post URLs (e.g. https://t.me/durov/491) or <channel>/<id> shorthand.
  2. The actor fetches each post the same way Telegram's public web preview does, then assembles a flat JSON record.
  3. Results stream into your dataset, ready to download as JSON, CSV, or Excel.

You do not need to manage scrapers, browsers, or rotating IPs — all handled internally.

Input

{
"posts": [
"https://t.me/durov/491",
"https://t.me/telegram/350"
],
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["DATACENTER"]
}
}
FieldTypeDescription
postsarrayList of Telegram post URLs or <channel>/<id> shorthand. Both https://t.me/durov/491 and durov/491 are accepted.
proxyConfigurationobjectApify Proxy settings. Datacenter proxy works for most public Telegram posts.

Output

Input: https://t.me/durov/491

{
"id": 491,
"channel": "durov",
"url": "https://t.me/durov/491",
"text": "🇪🇺\nThe EU wants to force mandatory ID checks on anyone using social media — and ban people under 18 from accessing it. To that end, the EU Commission spent over a year building an \"age verification app\", which its president pompously unveiled yesterday.\nToday, this app\ngot hacked\nin just 2 minutes\n. ... (truncated)",
"datetime": "2026-04-17T02:31:54+00:00",
"views": "2.93M",
"author": "Pavel Durov",
"forwardedFrom": null,
"replyTo": null,
"photos": [],
"videos": [],
"links": [
"https://cybernews.com/security/eu-age-verification-app-hack/"
],
"reactions": [],
"_input": "https://t.me/durov/491",
"_source": "S1-html",
"_scrapedAt": "2026-05-18T10:39:59.180138+00:00"
}
FieldTypeDescription
_inputstringThe URL or shorthand exactly as you supplied it. Use this to join results back to your input list.
_sourcestringInternal tag for the path used to fetch the record. S1-html means the post was extracted from Telegram's public web preview.
_scrapedAtstringISO-8601 UTC timestamp when the record was scraped.
idintegerTelegram message ID (numeric, scoped to the channel).
channelstringChannel username (the <channel> segment from the URL).
urlstringCanonical t.me/<channel>/<id> URL of the post.
textstringFull message text with newlines preserved. May contain emoji and unicode. null if the post is media-only.
datetimestringISO-8601 UTC timestamp the message was originally posted.
viewsstringPublic view count exactly as Telegram displays it (e.g. "2.93M", "154.2K", "812").
authorstringDisplay name of the channel or post author. null if Telegram does not expose one.
forwardedFromobjectIf the post is a forward, the original channel/user info; otherwise null.
replyToobjectIf the post replies to another message in the same channel, a reference to it; otherwise null.
photosarrayDirect URLs of photos attached to the post. CDN-signed and expire — mirror them immediately if you need long-term storage.
videosarrayDirect URLs of videos attached to the post. CDN-signed and expire.
linksarrayOutbound URLs found in the message body.
reactionsarrayEmoji reactions and their counts, when shown publicly.

Error envelope

Posts that cannot be parsed return a structured error instead of crashing the run:

{
"_input": "https://t.me/private-channel/1",
"_channel": "private-channel",
"_messageId": 1,
"_error": "not_found",
"_errorDetail": "Telegram NotFound",
"_source": "S1-html",
"_scrapedAt": "2026-05-18T10:40:02.512345+00:00"
}

Filter on _error to triage failed rows. Common values: invalid_input, not_found, fetch_failed, parse_failed.

Pricing

This actor is billed per result: $2.50 per 1,000 results. Each successfully scraped post = 1 result. Errors (not-found, private channel, parse failures) are not billed.

Other Sosmed Actors

PlatformActorBest for
TelegramTelegram Channel Posts ScraperPull a feed of recent posts from any public channel
BlueskyBluesky Post Detail ScraperSingle AT-Protocol post by URL
RedditReddit Post Detail ScraperSingle Reddit submission + comments
MastodonMastodon Status Detail ScraperSingle Mastodon status by URL
ThreadsThreads Post Detail ScraperSingle Threads post by URL
InstagramInstagram Post Detail ScraperSingle Instagram post (photo, reel, carousel)
X / TwitterX Post Detail ScraperSingle tweet by URL

Browse the full catalog at apify.com/xtracto.

Notes

  • Only public channels are accessible. Private/invite-only channels and personal chats are out of scope and return _error: "not_found".
  • Some channels are flagged with content restrictions in the public web view (If you have Telegram...); those return an _error envelope rather than partial data.
  • Photo and video URLs are CDN-signed and expire — download or mirror them immediately if you need long-term storage.
  • The public preview occasionally drops formatting (bold, italics, custom emoji) for very recent posts; structured fields (id, views, datetime, text) remain reliable.
  • View counts are eventually-consistent and may lag the live channel by a few minutes.