# Telegram Channel Posts Scraper (`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:** [Ilia Muravev](https://apify.com/chorelet) (community)
- **Categories:** Social media, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 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 Posts Scraper

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/<channel>`, 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.

### 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/<channel>/<id>`, 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:<id>`, 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`.

### 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.
- **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.

### Pricing

Pay per post, nothing else — you only pay for what lands in the dataset. Runs that return zero posts cost nothing.

### Typical uses

Monitoring news and competitor channels, feeding posts into an LLM for summaries or sentiment, tracking reach (views/reactions) of a channel over time, archiving a channel, content research for marketing — via CSV/Excel, Google Sheets, or the Apify API and integrations (Zapier, Make, n8n).

# 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.

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

// Prepare Actor input
const input = {
    "channels": [
        "telegram",
        "durov"
    ],
    "maxPostsPerChannel": 100,
    "postedAfter": "30 days",
    "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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "channels": [
        "telegram",
        "durov",
    ],
    "maxPostsPerChannel": 100,
    "postedAfter": "30 days",
    "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": "30 days",
  "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 <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/BiB0oFhHpWv9e2kRC/builds/v8Zyqw68DrMWOMSgO/openapi.json