# Telegram Channel Scraper — Posts, Views, Reactions, No Login (`chorelet/telegram-channel-posts-scraper`) Actor Scrape posts from public Telegram channels without login: text, date, views, reactions, media, forwards, replies, polls and link previews — newest first, with date filter and CSV/JSON export. - **URL**: https://apify.com/chorelet/telegram-channel-posts-scraper.md - **Developed by:** [Chorelet](https://apify.com/chorelet) (community) - **Categories:** Social media, Automation, Developer tools - **Features:** Limited permissions - **Stats:** 18 total users, 5 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.35 / 1,000 posts This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Telegram Channel Scraper — Posts, Views, Reactions, No Login Get the latest posts from any **public Telegram channel** — no login, no API keys, no phone number. Paste channel names or links, set how many posts you need (or a date like "30 days"), and download text, views, reactions, media and forwards as JSON, CSV or Excel, or pull them via API into your own tools. Reads the same public web preview that opens at `t.me/s/`, so it works for every channel that has the preview enabled — and only collects what the channel itself shows to the public. It never collects members, phone numbers or private chats. ### Why this Actor - No Telegram account, API keys or phone number — reads the public web preview of each channel - **Built for a schedule.** *Only new since the last run* remembers where each channel stopped, so an hourly or daily run returns just what appeared — no duplicates, no date arithmetic, nothing to pay for when nothing was posted. - Views, reactions (including custom emoji), forwards, replies, albums, documents, polls and link previews in one schema - `postedAfter: "1 day"` stops at the first old post, so daily monitoring costs cents - Channel aliases and disabled previews handled with clear messages - Checked every day by an automated run; fixed within 24 hours when Telegram changes its markup ### Sample output One item of the dataset (long values shortened): ```json { "channel": "durov", "channelTitle": "Pavel Durov", "channelSubscribers": 10400000, "id": 552, "url": "https://t.me/durov/552", "date": "2026-10-11T14:52:40.000Z", "text": "✨ Designers × AI\n\n🆕 The mockup era is over. Today’s AI tools give every designer a superpower: you can now craft your ideas, not just dra…", "views": 753000, "reactions": [ { "emoji": "⭐", "count": 5220 }, { "emoji": "custom:5936157098181135162", "count": 9990 }, { "emoji": "custom:5399847211989246390", "count": 4410 }, "…" ], "reactionsTotal": 22920, "forwardedFrom": { "name": "Telegram Designers", "url": "https://t.me/designers/266" }, "mediaTypes": [ "video" ], "photos": [], "links": [ { "text": "@designers", "url": "https://t.me/designers" } ] } ``` ### What you get | Field | Description | |---|---| | `channel`, `channelTitle`, `channelSubscribers` | Channel username, title and subscriber count at scrape time | | `id`, `url`, `date`, `edited` | Post ID, `https://t.me//`, posting time (UTC) | | `text` | Plain text with line breaks (null for media-only posts) | | `author` | Author signature, when the channel signs posts | | `views`, `reactions`, `reactionsTotal` | Views and reactions as Telegram displays them (`1.2K` → `1200`); custom emoji appear as `custom:`, Telegram Stars as ⭐ | | `forwardedFrom`, `replyTo` | Source of a forward; quoted post for replies | | `mediaTypes`, `isAlbum`, `photos`, `videos`, `documents`, `voices`, `stickers`, `poll` | Media attached to the post (CDN links, video duration, document name and size, poll options and percentages) | | `linkPreview` | Site name, title, description and image of the previewed link | | `links`, `hashtags`, `mentions` | Extracted from the text | Posts come **newest first** per channel. A per-channel summary (title, subscribers, posts fetched, errors) is saved to the key-value store as `SUMMARY`. **Only new since the last run.** Turn it on and the Actor remembers the newest post it returned for every channel and starts the next run there — a schedule then gives you a clean feed of what appeared since last time, with no duplicates to filter out and nothing to charge for when a channel was quiet. The state lives in a key-value store on your own account, one per task, so two schedules never overwrite each other. ### Input - **Channels** — any mix of `durov`, `@telegram`, `https://t.me/telegram`, `t.me/s/tproger`. - **Max posts per channel** — newest first; one page of history is 20 posts. - **Only posts newer than** — `2026-01-31` or `7 days` / `2 weeks` / `3 months` / `1 year`. Scraping stops at the first older post, so a daily run with `1 day` costs almost nothing. - **Only new since the last run** — for schedules: each run continues from the newest post the previous one saved. - **Watch key** — leave empty; it keeps one saved state per task. Set it by hand to share a state between tasks, or change it to start from scratch. - **Proxy** — off by default; Telegram serves the preview freely. Turn on Apify datacenter proxies only for very large runs. ### Limits and notes - Only **public channels with web preview** can be read. Private channels, invite links (`t.me/+…`), bots and groups return "not a public channel, or its web preview is disabled". - Counts are the rounded numbers Telegram shows publicly. Media URLs point to Telegram's CDN and can expire — download them promptly if you need the files. - Comments (discussion groups) are not included. - Public data only; the Actor stores nothing beyond the dataset of your run. ### Input example ```json { "channels": [ "telegram", "durov" ], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": false } ``` ### How much does it cost? Pay per post — no subscription, no minimum, no charge for platform usage. | Volume | Price | |---|---| | 1,000 posts | $0.50 | | 10,000 posts | $5.00 | | 100,000 posts | $50.00 | The Apify **free plan includes $5 of usage every month** — about 10,000 posts with this Actor, no card needed. Nothing else is charged: platform usage is included in the price, and Apify Bronze, Silver and Gold subscribers get 10%, 20% and 30% off these prices. ### Use it from code, n8n, Make, Zapier or an AI agent Run the Actor and download the dataset in one call (JSON by default; add `&format=csv` or `xlsx`): ```bash curl -X POST "https://api.apify.com/v2/acts/chorelet~telegram-channel-posts-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"channels": ["telegram", "durov"], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": false}' ``` Python: ```python from apify_client import ApifyClient client = ApifyClient("YOUR_APIFY_TOKEN") run = client.actor("chorelet/telegram-channel-posts-scraper").call(run_input={"channels": ["telegram", "durov"], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": false}) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) ``` - **n8n, Make, Zapier** — use the Apify node/module: run the Actor, then "get dataset items". - **Google Sheets, Slack, webhooks** — add an integration on the run's *Integrations* tab. - **AI agents** — the Actor is available as a tool through the Apify MCP server; the dataset schema describes every field for the model. - **Schedules** — run it hourly, daily or weekly from the *Schedules* tab. ### Tutorials - [Export any public Telegram channel to CSV or JSON in 5 minutes — no API keys, no phone number](https://dev.to/chorelet/export-any-public-telegram-channel-to-csv-or-json-in-5-minutes-no-api-keys-no-phone-number-1d47) (Dev.to) ### FAQ **Which channels can be scraped?** Any public channel that has a web preview at t.me/s/ — the vast majority. Private channels, invite links and groups without a preview are reported as unavailable and the run continues. **Do I need a Telegram account or API keys?** No. The Actor reads the same public preview pages that open in a browser without logging in. **Can I get only the posts that appeared since my last run?** Yes — switch on *Only new since the last run*. The Actor remembers the newest post id per channel in a key-value store on your account and starts there next time, so a schedule returns a clean feed and quiet channels cost nothing but the run start. **How far back can I go?** All the way to the first post; history is read 20 posts per page. Use `maxPostsPerChannel` or `postedAfter` to stop earlier. **Are views and reactions exact?** They are the rounded numbers Telegram shows publicly (1.2K → 1200, 18.8M → 18800000). **Are comments included?** No — discussion-group comments are not part of the public preview. **What does a run cost?** $0.50 per 1,000 posts. The Apify free plan's $5 a month covers about 10,000 posts. ### Support Questions, missing fields or a source that changed? Open an issue on the *Issues* tab or write to support@chorelet.app — problems are usually fixed within a day, and the Actor is checked every morning by an automated test run. If the Actor saved you time, a short review on its Store page helps other people find it. # Actor input Schema ## `channels` (type: `array`): Public channel usernames or links: `durov`, `@telegram`, `https://t.me/telegram`, `t.me/s/tproger`. Private channels, invite links and groups without a web preview cannot be read. ## `maxPostsPerChannel` (type: `integer`): Newest posts first. One page of history is 20 posts, so 100 posts = 5 requests. ## `postedAfter` (type: `string`): Absolute date `2026-01-31` or relative `7 days`, `2 weeks`, `3 months`, `1 year`. Scraping stops at the first older post. Leave empty for no date limit. ## `onlyNew` (type: `boolean`): Saves only posts that earlier runs did not return. The state is kept in a key-value store on your own account, so a scheduled run gives you a clean feed of what appeared since last time — and a run that finds nothing new costs only the run start. ## `watchKey` (type: `string`): Which saved state to continue. Empty = one state per task, so two schedules of this Actor never overwrite each other. Set it by hand to share one state between tasks, or change it to start over. ## `proxyConfiguration` (type: `object`): Off by default — t.me serves public previews without a proxy. Enable Apify datacenter proxies only if you scrape hundreds of channels per run and start seeing HTTP 429. ## Actor input object example ```json { "channels": [ "telegram", "durov" ], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": false, "watchKey": "", "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `posts` (type: `string`): All scraped posts — items of the default dataset. Use ?format=csv or xlsx on this URL for spreadsheets. ## `summary` (type: `string`): Channel title, subscribers and number of posts fetched per channel, plus errors. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "channels": [ "telegram", "durov" ], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": false, "watchKey": "", "proxyConfiguration": { "useApifyProxy": false } }; // Run the Actor and wait for it to finish const run = await client.actor("chorelet/telegram-channel-posts-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "channels": [ "telegram", "durov", ], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": False, "watchKey": "", "proxyConfiguration": { "useApifyProxy": False }, } # Run the Actor and wait for it to finish run = client.actor("chorelet/telegram-channel-posts-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "channels": [ "telegram", "durov" ], "maxPostsPerChannel": 100, "postedAfter": "90 days", "onlyNew": false, "watchKey": "", "proxyConfiguration": { "useApifyProxy": false } }' | apify call chorelet/telegram-channel-posts-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,chorelet/telegram-channel-posts-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/BiB0oFhHpWv9e2kRC/builds/EeEvZ6ebYpVc0GchG/openapi.json