Telegram Post Detail Scraper
Pricing
from $1.00 / 1,000 results
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
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
7 days ago
Last modified
Categories
Features
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,_scrapedAtenvelope fields so you can join results back to your input list.
How it works
- You provide a list of Telegram post URLs (e.g.
https://t.me/durov/491) or<channel>/<id>shorthand. - The actor fetches each post the same way Telegram's public web preview does, then assembles a flat JSON record.
- 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"]}}
| Field | Type | Description |
|---|---|---|
posts | array | List of Telegram post URLs or <channel>/<id> shorthand. Both https://t.me/durov/491 and durov/491 are accepted. |
proxyConfiguration | object | Apify 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"}
| Field | Type | Description |
|---|---|---|
_input | string | The URL or shorthand exactly as you supplied it. Use this to join results back to your input list. |
_source | string | Internal tag for the path used to fetch the record. S1-html means the post was extracted from Telegram's public web preview. |
_scrapedAt | string | ISO-8601 UTC timestamp when the record was scraped. |
id | integer | Telegram message ID (numeric, scoped to the channel). |
channel | string | Channel username (the <channel> segment from the URL). |
url | string | Canonical t.me/<channel>/<id> URL of the post. |
text | string | Full message text with newlines preserved. May contain emoji and unicode. null if the post is media-only. |
datetime | string | ISO-8601 UTC timestamp the message was originally posted. |
views | string | Public view count exactly as Telegram displays it (e.g. "2.93M", "154.2K", "812"). |
author | string | Display name of the channel or post author. null if Telegram does not expose one. |
forwardedFrom | object | If the post is a forward, the original channel/user info; otherwise null. |
replyTo | object | If the post replies to another message in the same channel, a reference to it; otherwise null. |
photos | array | Direct URLs of photos attached to the post. CDN-signed and expire — mirror them immediately if you need long-term storage. |
videos | array | Direct URLs of videos attached to the post. CDN-signed and expire. |
links | array | Outbound URLs found in the message body. |
reactions | array | Emoji 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
| Platform | Actor | Best for |
|---|---|---|
| Telegram | Telegram Channel Posts Scraper | Pull a feed of recent posts from any public channel |
| Bluesky | Bluesky Post Detail Scraper | Single AT-Protocol post by URL |
| Reddit Post Detail Scraper | Single Reddit submission + comments | |
| Mastodon | Mastodon Status Detail Scraper | Single Mastodon status by URL |
| Threads | Threads Post Detail Scraper | Single Threads post by URL |
| Instagram Post Detail Scraper | Single Instagram post (photo, reel, carousel) | |
| X / Twitter | X Post Detail Scraper | Single 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_errorenvelope 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.