# Telegram Channel Scraper - Posts, Views, Media (no login) (`obliging_resilience/telegram-channel-scraper`) Actor

Scrape posts, views, reactions, media links and forwards from public Telegram channels via the public t.me/s preview. No login, no API keys.

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

## Pricing

from $1.50 / 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 (public posts, no login)

You get **public Telegram channel posts as clean JSON/CSV**: text, date, views, reactions, media, link previews, forwards and channel info. No Telegram account, no API key, no phone number.
**Price: $1.50 per 1,000 posts** (pay per event: `post` = $0.0015). Error rows are free.

### Why use it

- **News and crypto/tech monitoring**: pull the newest posts of the channels you follow every day and feed them to a dashboard or alert.
- **Brand and media mentions**: collect posts with views and reactions to see which messages spread.
- **Research datasets**: build text datasets for sentiment analysis or topic models (public posts only).

### Input

| Field | Description |
|---|---|
| `channels` | Public channels: `durov`, `@durov`, `https://t.me/durov` or `https://t.me/s/durov` (required) |
| `maxPosts` | Max posts per channel, newest first (default 100, max 100000) |
| `since` | Optional ISO date such as `2026-01-01`. Older posts are skipped |

```json
{
  "channels": ["durov", "https://t.me/telegram"],
  "maxPosts": 200,
  "since": "2026-06-01"
}
```

Error row example: `{ "channel": "ab", "error": "Not a valid public channel username or t.me URL." }`

### Example output

| channel | postId | url | date | views | viewsRaw | text | hashtags | forwardedFrom |
|---|---|---|---|---|---|---|---|---|
| durov | 552 | https://t.me/durov/552 | 2026-10-11T14:52:40.000Z | 1190000 | 1.19M | Designers × AI ... | \[] | null |

`forwardedFrom` is `null` unless the post is a forward (then `{ name, url }`). Every row also has `edited`, `author`, `links`, `linkPreview`, `replyTo`, `isServiceMessage`, `reactions` (`type`, `emoji`, `emojiId`, `count`, `countRaw`), `media` (`type`, `thumbnail`, `duration`), `scrapedAt`, and `channelInfo` (`title`, `username`, `verified`, `subscribers`) on the first post of each channel.

```json
{
  "channel": "durov", "postId": 552, "url": "https://t.me/durov/552",
  "date": "2026-10-11T14:52:40.000Z", "edited": false, "author": "Pavel Durov",
  "text": "Designers × AI ...", "links": ["https://t.me/designers"], "hashtags": [],
  "views": 1190000, "viewsRaw": "1.19M",
  "reactions": [{ "type": "paid_stars", "emoji": null, "count": 5940, "countRaw": "5.94K" }],
  "media": [{ "type": "video", "thumbnail": "https://cdn4.telesco.pe/...", "duration": "1:15" }],
  "scrapedAt": "2026-10-20T05:33:26.281Z",
  "channelInfo": { "title": "Pavel Durov", "username": "durov", "verified": true, "subscribers": 10300000 }
}
```

### Use with AI agents / MCP

Call this actor from any AI agent through the Apify MCP server (`https://mcp.apify.com`) or the Apify API, using the actor id `Mu7P8m9K4dQ1LagwJ`. An agent can ask "what did these channels post this week and which posts got the most views?". Output is flat JSON with stable ids (`channel` + `postId`), so an agent can sort by `views`, filter by `hashtags` or summarise `text` directly. For daily monitoring, schedule the actor with `since` set to yesterday.

Sample tool input an agent can send:

```json
{
  "channels": ["durov", "telegram"],
  "maxPosts": 50,
  "since": "2026-10-14"
}
```

### Limits and notes

- Only channels with a public preview at `t.me/s/<name>`. No private channels, groups, comments or member lists.
- History depth is whatever the public preview shows. Use `maxPosts` and `since` to bound the run.
- Plain HTTP, rate-limited, no proxies needed for normal volumes.
- Set a maximum cost per run in the run options; the actor stops cleanly when it is reached.

### FAQ

**Can it scrape private channels or groups?** No. Only public previews.

**Does it get comments or member lists?** No. Only what the public preview shows.

**Why fewer posts than expected?** The channel may have fewer posts, or the `since` date was reached.

### Disclaimer

This is an **unofficial** tool. It is not affiliated with, endorsed by or sponsored by Telegram. It collects only publicly available data from Telegram's public web preview, with no login. You are responsible for using the data in line with Telegram's terms and applicable law (for example GDPR). Telegram can change its pages at any time, which may temporarily break the actor.

**AI disclosure:** this actor was built with AI assistance (Claude by Anthropic) and is maintained by tinygrid. Issues and feature requests are welcome in the Issues tab.

# Actor input Schema

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

Public channel usernames or URLs, e.g. durov, @durov, https://t.me/durov or https://t.me/s/durov.

## `maxPosts` (type: `integer`):

Newest posts first. Stops earlier if the channel has fewer posts or the 'since' date is reached.

## `since` (type: `string`):

Optional. ISO date like 2026-01-01. Older posts are skipped. Leave empty for no date limit.

## Actor input object example

```json
{
  "channels": [
    "durov"
  ],
  "maxPosts": 100
}
```

# Actor output Schema

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

Public Telegram channel posts and per-channel error records stored in the default dataset.

# 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"
    ],
    "maxPosts": 100
};

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

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

```

## MCP server setup

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