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

Scrape public Telegram channels without a login: posts, views, reactions, forwards, media and links in one clean format. Search inside a channel, filter by date, and use the built-in monitor to get only new posts.

- **URL**: https://apify.com/webobsidians/telegram-channel-scraper.md
- **Developed by:** [Web Obsidians](https://apify.com/webobsidians) (community)
- **Categories:** Social media, News
- **Features:** 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 posts

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

Get the posts of **public Telegram channels** in one clean format: text, date, views, reactions, forwards, replies, links, hashtags and media links. Paste channel names or links, optionally search inside a channel or set a date range, and download the result.

Turn on **Return only new posts** and schedule the Actor to monitor channels: each run returns only the posts that appeared since the last run.

### Why this Actor

- **No login, no phone number, no API keys.** It reads the public web preview that Telegram publishes for public channels (`t.me/s/<channel>`). No browser, no proxies.
- **The numbers that matter.** Views, reactions (emoji, custom emoji and paid Stars), the channel's subscriber count, forwarded-from, reply target, author signature and an edited flag come with every post (empty when a post has none).
- **Search and date range.** Use Telegram's own search inside a channel, or stop at a date.
- **Monitoring built in.** The monitor remembers the newest post it returned and gives you only newer posts on the next run, oldest first.
- **Cheap and predictable.** $1.00 per 1,000 posts. Platform usage is included.

### Use cases

- **Brand, crypto and news monitoring:** watch channels for new posts, or for posts that mention a word, and send them to Slack or a webhook.
- **Research:** collect posts, views and reactions to compare channels, topics or time periods.
- **Content tracking:** see which posts of a channel get the most views and reactions.
- **AI agents and analysis:** give your agent clean post text with links and dates.

### How to use

1. Add channels to **Channels**, one per line: `durov`, `@durov` or `https://t.me/durov`.
2. Optionally set a search word, a date range, or how many posts you want per channel.
3. Click **Start**. Download the results as JSON, CSV or Excel, or send them on with Apify integrations and webhooks (for example to Slack).

#### Input example

```json
{
  "channels": ["durov", "telegram"],
  "maxPostsPerChannel": 50,
  "searchQuery": "update",
  "dateFrom": "2026-11-01"
}
```

#### Get only new posts every hour

Set **Return only new posts** to on and give the monitor a name (for example `crypto-news`). Then create a schedule in Apify Console. The first run returns the latest posts and remembers where it stopped. Each later run returns only posts that are newer than the last post it returned, oldest first. If a run could not return everything (your per-channel limit or your maximum cost per run was reached), the rest is returned by the next run. You pay only for the posts that are returned.

### Output

Each post is one item in the dataset. This is a real item from a run of this Actor, shortened (the `links` list is cut):

```json
{
  "channel": "telegram",
  "channelTitle": "Telegram News",
  "channelSubscribers": 9090000,
  "postId": 460,
  "url": "https://t.me/telegram/460",
  "date": "2026-08-26T19:12:34Z",
  "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\n\nAugust Features\n1 • 2 • 3 • 4 • 5 • More",
  "views": 2640000,
  "reactions": [],
  "reactionsTotal": 0,
  "forwardedFrom": null,
  "forwardedFromUrl": null,
  "replyToUrl": null,
  "author": null,
  "edited": false,
  "links": [
    "https://telegram.org/blog/welcome-messages-buttons-TG-13",
    "https://t.me/telegram/455"
  ],
  "hashtags": [],
  "media": [
    {
      "type": "link_preview",
      "url": "https://telegram.org/blog/welcome-messages-buttons-TG-13"
    }
  ],
  "scrapedAt": "2026-11-19T04:42:32Z"
}
```

Reactions look like this (real examples from two other channels, shortened):

```json
[
  { "emoji": "🤣", "count": 116 },
  { "emoji": null, "count": 34700, "customEmojiId": "5399847211989246390" },
  { "emoji": "⭐", "count": 17100, "paid": true }
]
```

Field notes:

- `date` and `scrapedAt` are UTC.
- `views`, reaction counts and `channelSubscribers` are whole numbers. Telegram rounds large numbers on its public page (it shows `4.45M`, which becomes `4450000`).
- `reactions` lists what the post shows: normal emoji, custom emoji (`emoji` is `null` and `customEmojiId` identifies it) and paid Star reactions (`paid: true`). `reactionsTotal` adds up the emoji reactions and leaves out paid Stars. Some channels show no reactions on the public page; then `reactions` is an empty list.
- `forwardedFrom` and `forwardedFromUrl` are `null` for posts that are not forwards, and also for forwards whose original source Telegram does not show.
- `replyToUrl` is the post this post replies to. `author` is the signature of the admin who wrote the post, when the channel shows one. `edited` is `true` for posts that were edited.
- `links` are the links in the post text. `hashtags` are the hashtags in the text, with the `#`.
- `media` lists `photo`, `video`, `document`, `poll` and `link_preview` items. For photos, videos and link cards `url` is the file or the page that Telegram links. For a document, a poll, or a video that is too big to play on the public page, `url` is the post itself.
- A per-channel summary (title, subscribers, posts returned, any error) is saved to the key-value store as `SUMMARY`.

### Pricing

This Actor uses pay-per-event pricing:

- **$1.00 per 1,000 posts** saved to the dataset ($0.001 per post).
- **$0.00005 per run start.**

Platform usage (compute and storage) is included. For example, 100 posts cost about $0.10, and an hourly monitor that returns 5 new posts a day costs about $0.19 a month ($0.15 for 150 posts plus $0.04 for 720 run starts). If you set a maximum cost per run, the Actor stops cleanly when it is reached.

### FAQ

**Which channels work?**
Public channels that have a web preview at `t.me/s/<name>`. Private channels, groups, invite links (`t.me/+...`), bots and channels that turned the preview off do not work. They are reported in `SUMMARY` with an error and cost nothing.

**Do I need a Telegram account or phone number?**
No. The Actor reads the same page you can open in any browser without logging in.

**What does it not get?**
Member lists, private chats and the comments under posts. It returns only the posts that the channel's public page shows.

**How many posts can I get?**
Up to 10,000 posts per channel in one run, newest first. Telegram's page shows about 20 posts at a time and the Actor pauses between pages, so a large run takes a few minutes.

**How does the date range work?**
`dateFrom` and `dateTo` are UTC days (for example `2026-11-01`) and both days are included. The Actor reads from the newest post backwards and stops when it reaches `dateFrom`.

**What if a channel posts more than 2,000 times between two monitor runs?**
Each monitor run looks at the newest 2,000 posts that are newer than the last returned one. Run the monitor more often for very busy channels.

**Why are some counts different from what I see in the app?**
Telegram's public page shows rounded counts (for example `12.3K`), and the Actor reports exactly what the page shows.

# Actor input Schema

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

One public channel per line: a name (durov), @durov, or a link (https://t.me/durov). Only public channels that have a web preview at t.me/s/<name> work. Private channels, groups and invite links do not.

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

Stop after this many posts per channel, newest first. 0 means no limit, but at most 10,000 posts per channel are returned in one run.

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

Return only posts that match this word or phrase, using Telegram's own search for the channel.

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

Skip posts older than this day. Format YYYY-MM-DD, UTC, for example 2026-11-01.

## `dateTo` (type: `string`):

Skip posts newer than this day (this day is included). Format YYYY-MM-DD, UTC.

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

Return only posts that are newer than the ones returned by earlier runs with the same monitor name. The first run returns the latest posts and remembers where it stopped.

## `monitorName` (type: `string`):

Use different names to keep separate histories, for example one per client or per topic.

## Actor input object example

```json
{
  "channels": [
    "durov",
    "telegram"
  ],
  "maxPostsPerChannel": 20,
  "onlyNewPosts": false,
  "monitorName": "default"
}
```

# Actor output Schema

## `posts` (type: `string`):

No description

## `summary` (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"
    ],
    "maxPostsPerChannel": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("webobsidians/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",
    ],
    "maxPostsPerChannel": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("webobsidians/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"
  ],
  "maxPostsPerChannel": 20
}' |
apify call webobsidians/telegram-channel-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,webobsidians/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/OhW08aE0k8GWlDW31/builds/I6Xq7MrYwEgdMvEYT/openapi.json
