# Telegram Channel Scraper: Posts, Views, Reactions & Media (`classier_wholemeal/telegram-channel-scraper`) Actor

Scrape any public Telegram channel without an account, phone number or API keys. Get posts with full text, views, reactions, media URLs, links, hashtags, forwards and channel stats (subscribers, verified). Date range, keyword search, new-posts-only monitoring. Fast and cheap: $1 per 1,000 posts.

- **URL**: https://apify.com/classier_wholemeal/telegram-channel-scraper.md
- **Developed by:** [JackKnifeAI](https://apify.com/classier_wholemeal) (community)
- **Categories:** Social media, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 post scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 & Media (No Login)

Scrape **any public Telegram channel** without a Telegram account, phone number, API ID or bot token. Get every post's **full text, views, reactions, media URLs, links, hashtags, mentions and forwards**, plus **channel stats** such as subscribers, verified status and media counts. You can filter by **date, keyword and minimum views**, search inside a channel, and run in **monitoring mode** so each run returns **only new posts**.

**$1 per 1,000 posts**, about 5x cheaper than most Telegram scrapers.

### Use cases

- **Crypto and trading signal research:** collect posts, views and reactions from signal and news channels.
- **Brand, news and OSINT monitoring:** schedule hourly runs with `onlyNewPosts` to get only fresh posts, then send them to Slack, Sheets or a webhook.
- **Influencer and channel analytics:** compare subscribers, views per post and engagement across competitor channels.
- **Datasets for NLP or AI:** export clean post text with dates and engagement as JSON, CSV or Excel.
- **Lead generation:** extract the links, @mentions and hashtags that channels share.

### Features

- ✅ No login, no phone number, no Telegram API keys
- ✅ Many channels per run, with full history paging (tested at 1,000+ posts per channel)
- ✅ Views, reactions with counts, paid stars, author signature and edited flag
- ✅ Photos, videos, video thumbnails, documents, polls and link previews
- ✅ Forwarded-from channel, reply-to links, hashtags, mentions and outbound links
- ✅ Search posts inside a channel (`searchQuery`)
- ✅ Filters: last N days, from date, keywords, minimum views, exclude forwards. Filtered-out posts are free.
- ✅ Monitoring mode (`onlyNewPosts`) remembers the last post per channel between runs
- ✅ A channel info row with subscribers, description, photo and media counts

### Input

| Field | Description |
|---|---|
| `channels` | Usernames or links: `durov`, `@telegram`, `https://t.me/durov`, `https://t.me/s/durov` |
| `maxPostsPerChannel` | Newest first, default 100 |
| `searchQuery` | Optional search within each channel |
| `postedWithinDays` / `dateFrom` | Date limits |
| `keywords` | Keep posts containing any of these words |
| `minViews` | Keep posts with at least this many views |
| `excludeForwarded` | Skip forwarded posts |
| `onlyNewPosts` | Return only posts newer than the previous run |
| `stateStoreName` | Name of the key-value store used for monitoring state. Use a different name for each separate monitor. |
| `includeChannelInfo` | Add one channel row per channel (default true) |
| `proxyConfiguration` | Optional Apify proxy |

#### Example: last 7 days from several channels, popular posts only (10k+ views)

```json
{
  "channels": ["durov", "telegram", "https://t.me/bbcrussian"],
  "postedWithinDays": 7,
  "minViews": 10000,
  "maxPostsPerChannel": 500
}
```

#### Example: hourly monitor for new posts mentioning bitcoin

```json
{
  "channels": ["durov", "telegram"],
  "keywords": ["bitcoin", "btc"],
  "onlyNewPosts": true,
  "stateStoreName": "my-btc-monitor"
}
```

### Output

Post row (`type: "post"`):

```json
{
  "type": "post",
  "channel": "durov",
  "postId": 551,
  "url": "https://t.me/durov/551",
  "date": "2026-10-10T14:22:43+00:00",
  "text": "💸 If your wallet doesn’t look like this, don’t even bother sending me money for my birthday! 🎂",
  "textLength": 95,
  "views": 2030000,
  "reactionsTotal": 61150,
  "reactions": [{"emoji": null, "customEmojiId": "5936157098181135162", "count": 38200}],
  "paidStars": 60300,
  "author": "Pavel Durov",
  "mediaType": "video",
  "photos": [],
  "videos": ["https://cdn4.telesco.pe/file/...mp4"],
  "documents": [],
  "links": [],
  "hashtags": [],
  "mentions": [],
  "isForwarded": false,
  "forwardedFrom": null,
  "replyToUrl": null,
  "channelTitle": "Pavel Durov",
  "channelSubscribers": 10100000,
  "scrapedAt": "2026-11-04T04:39:04+00:00"
}
```

Channel row (`type: "channel"`):

```json
{
  "type": "channel",
  "username": "durov",
  "url": "https://t.me/durov",
  "title": "Pavel Durov",
  "verified": true,
  "description": "Founder of Telegram.",
  "subscribers": 10100000,
  "photos": 102,
  "videos": 47,
  "links": 200
}
```

A private, deleted or non-existent channel produces a free `type: "error"` row, and the run continues.

The **Posts** and **Channels** tabs show tables. You can export JSON, CSV, Excel or HTML, or connect the API, Make, Zapier, n8n, Google Sheets or webhooks.

### Pricing (pay per event)

- **$0.001 per post**, which is $1 per 1,000 posts
- **$0.002 per channel info row**
- Posts removed by your filters are **free**.
- Set a *maximum cost per run* and the actor stops cleanly when it's reached.

### Limits

- Works only with **public channels** that have a web preview at `t.me/s/<name>`. Private groups, invite links (`t.me/+...`) and chats aren't supported.
- Media URLs are Telegram CDN links that expire after a while. Download the files soon after scraping if you need them.
- Comment threads aren't included.

### FAQ

**Do I need a Telegram account or API keys?** No. The actor reads Telegram's public web preview.

**How do I get only new posts every hour?** Turn on `onlyNewPosts` and schedule the actor in Apify Schedules. Each run returns only posts published since the last run.

**Can I use it through the API?** Yes. Call `POST https://api.apify.com/v2/acts/classier_wholemeal~telegram-channel-scraper/run-sync-get-dataset-items` with the JSON input.

# Actor input Schema

## `channels` (type: `array`):

Public channel usernames or links, one per line: durov, @telegram, https://t.me/durov or https://t.me/s/durov. Private groups and invite links (t.me/+...) are not supported.

## `maxPostsPerChannel` (type: `integer`):

Newest posts first. The scraper pages back through the channel history until this limit or the date limit is reached.

## `postedWithinDays` (type: `integer`):

Stop when posts get older than this. Leave empty for no limit.

## `dateFrom` (type: `string`):

Stop at posts older than this date (YYYY-MM-DD). Optional.

## `searchQuery` (type: `string`):

Use Telegram's own in-channel search (e.g. a ticker, brand or keyword). Leave empty to get all posts.

## `keywords` (type: `array`):

Case-insensitive. A post is kept if it contains any of these words. Filtered-out posts are not charged.

## `minViews` (type: `integer`):

Skip posts with fewer views (not charged).

## `excludeForwarded` (type: `boolean`):

Skip posts forwarded from other channels (not charged).

## `onlyNewPosts` (type: `boolean`):

Remembers the newest post per channel in the key-value store. Schedule the Actor and you only get (and pay for) new posts. State is kept in a named key-value store (see below).

## `stateStoreName` (type: `string`):

Named key-value store that remembers the last post seen per channel. Use a different name per monitoring task. Default: telegram-channel-scraper-state.

## `includeChannelInfo` (type: `boolean`):

One extra row per channel: title, description, subscribers, photo/video/link counts, verified badge.

## `proxyConfiguration` (type: `object`):

Not needed for normal use. Enable Apify Proxy for very large jobs.

## Actor input object example

```json
{
  "channels": [
    "durov",
    "telegram"
  ],
  "maxPostsPerChannel": 100,
  "excludeForwarded": false,
  "onlyNewPosts": false,
  "includeChannelInfo": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "channels": [
        "durov",
        "telegram"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("classier_wholemeal/telegram-channel-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "channels": [
        "durov",
        "telegram",
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("classier_wholemeal/telegram-channel-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": [
    "durov",
    "telegram"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call classier_wholemeal/telegram-channel-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,classier_wholemeal/telegram-channel-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 <APIFY_API_TOKEN>` 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/z1nQzfoBKRtz9K0BJ/builds/w99zJyCYBmzwcOsU2/openapi.json