# Telegram Channel Scraper — Posts, Views, Media (No Login) (`apricot_blackberry/telegram-channel-scraper`) Actor

Scrape any public Telegram channel without login: posts, text, dates, views, forwards, links, media URLs and polls as clean JSON. $0.001 per post, no start fee.

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

## Pricing

$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 — Posts, Views, Media, Polls (No Login, $1 per 1,000 posts)

Scrape any **public Telegram channel** without an account, API key or phone number. Give it channel names or `t.me` links and get every post as clean JSON: text (plain and HTML), date, view count, forwards, replies, links, hashtags, media URLs and polls. Newest first, as far back as you ask.

**$0.001 per post.** No start fee, no charge for channels that cannot be read.

### What you get

One record per post:

```json
{
  "channel": "durov",
  "id": 531,
  "url": "https://t.me/durov/531",
  "date": "2026-07-16T20:45:25+00:00",
  "text": "Telegram now has a Rich Text Editor...",
  "textHtml": "<b>Telegram now has a Rich Text Editor.</b><br>...",
  "views": 5750000,
  "author": null,
  "forwardedFrom": null,
  "replyTo": null,
  "links": ["https://telegram.org/blog/..."],
  "hashtags": [],
  "media": [{ "type": "video", "url": "https://cdn4.telesco.pe/file/...", "duration": "0:42" }],
  "mediaCount": 2,
  "poll": null,
  "edited": false,
  "scrapedAt": "2026-10-06T05:10:00.000Z"
}
```

Channel metadata (title, description, subscriber count, photo) is saved in the `CHANNELS` key-value record.

### Input

| Field | Default | Notes |
|---|---|---|
| `channels` | — | Usernames or links: `durov`, `@telegram`, `https://t.me/s/bloomberg`. |
| `maxPostsPerChannel` | 100 | Newest first. |
| `sinceDate` | — | Stop at the first post older than this ISO date. |
| `includeMedia` | true | Photo/video/document/voice/sticker entries with URLs where Telegram exposes them. |
| `callbackUrl` | — | POST a JSON summary when the run finishes. |

### Limits

Only channels with a public preview (`t.me/s/<channel>`) can be read. Private channels, groups and user profiles are reported in `SUMMARY.failures` and not charged. Comments under posts are not included.

### Pricing

| Event | Price |
|---|---|
| `post` | $0.001 |

1,000 posts cost $1. Set **Max total charge** on the run to cap spend; the Actor stops cleanly when it is reached.

### Integrations

- **API**: `POST https://api.apify.com/v2/acts/apricot_blackberry~telegram-channel-scraper/run-sync-get-dataset-items?token=…` with `{"channels": ["durov"], "maxPostsPerChannel": 50}`.
- **MCP**: add `https://mcp.apify.com?tools=apricot_blackberry/telegram-channel-scraper` to Claude, Cursor or any MCP client.
- **Webhooks**: `callbackUrl` in the input, or Apify run webhooks for Zapier, Make and n8n.
- **Schedules**: run hourly or daily to monitor channels; use `sinceDate` to fetch only new posts.

# Actor input Schema

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

Public channel usernames or t.me links (e.g. durov, @telegram, https://t.me/s/bloomberg). Private channels and user profiles cannot be read.

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

Newest posts first. Each page of history holds about 20 posts.

## `sinceDate` (type: `string`):

ISO date (e.g. 2026-01-01). Scraping stops at the first older post.

## `includeMedia` (type: `boolean`):

Add photo, video, document, voice and sticker entries with URLs where Telegram exposes them.

## `callbackUrl` (type: `string`):

POST a JSON summary here when the run finishes.

## Actor input object example

```json
{
  "channels": [
    "durov",
    "telegram"
  ],
  "maxPostsPerChannel": 100,
  "includeMedia": true
}
```

# Actor output Schema

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

Dataset with one JSON record per result.

## `summary` (type: `string`):

Counts, failures and notes.

# 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"
    ]
};

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

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

```

## MCP server setup

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