# Telegram Channel Scraper: Posts, Views and Links (`usta/telegram-channel-posts`) Actor

For market-intelligence and brand-monitoring analysts: one row per public Telegram channel post from the signed-out web preview, with text, date, view count, links, media addresses and forwarded-from channel. No Telegram account.

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

## Pricing

$2.00 / 1,000 result rows

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 Public Channel Posts, Views and Links

This telegram scraper reads a public telegram channel and returns telegram posts with views, links, and media addresses from the signed-out web preview.

It opens `https://t.me/s/{channel}` the same way a signed-out browser does. It does not log in.

### Input

| Field | What it is |
|---|---|
| Channels | Public channel names or `t.me` / `t.me/s/` links. Default `durov`. |
| Since date | Optional. Only posts on or after this ISO date. |
| Maximum posts per channel | Default 50, hard ceiling 1000. Older pages are loaded with `?before=` on the lowest post number, one second apart. |
| Maximum rows | Spend cap. Default 100, hard ceiling 5000. |
| Proxy configuration | Apify Proxy. Off by default. |

### Output

One row per post. A channel that does not exist, or that has no public preview, returns one error row instead of invented posts.

| Field | What it holds |
|---|---|
| `channel` | Username you asked for |
| `channel_title` | Display name on the preview |
| `post_id` | Numeric post id |
| `post_url` | `https://t.me/{channel}/{id}` |
| `date` | ISO timestamp from the page |
| `text` | Post text. Emails and phone numbers are replaced with `[redacted]`. |
| `views` | View count as a number (`12.3K` becomes `12300`) |
| `links` | `http(s)` links inside the post text |
| `media_type` | `photo`, `video`, `document`, `voice`, or `sticker` when that media is on the page |
| `media_urls` | Addresses shown for that media |
| `forwarded_from` | Forwarded-from channel name when shown |
| `reply_to` | Replied-to post id when shown |
| `edited` | `true` when the preview prints `edited` |
| `error` / `message` | Set only when that channel could not be read |

### Example row

From a live local run on 2026-09-20, input `durov`, maximum 5 posts. The run returned **5** rows. One of them:

```json
{
  "channel": "durov",
  "channel_title": "Pavel Durov",
  "post_id": 548,
  "post_url": "https://t.me/durov/548",
  "date": "2026-09-11T16:04:02+00:00",
  "text": "🤝 Telegram has become the sponsor of Codeforces — the largest competitive programming platform in the world.\n⚡CodeForces organizes over 100 coding contests every year and has 4 million contestants signed up.\n🌱 Since 2010, I've supported Codeforces through the companies I started.\n🆚 But this year will be special. Its founder Mike wants to bring Codeforces to the next level — and we'll be happy to help him do that 🤝",
  "views": 1350000,
  "links": [
    "https://codeforces.com/blog/entry/156620"
  ],
  "media_type": null,
  "media_urls": [],
  "forwarded_from": null,
  "reply_to": null,
  "edited": false,
  "error": null,
  "message": null,
  "http_status": null,
  "source_url": "https://t.me/s/durov",
  "fetched_at": "2026-09-21T00:56:16Z"
}
```

### Pricing

**Pay per result.** Each post row (and each honest error row) is one result. There is no start fee in this package. A run that returns no rows costs nothing. **Maximum rows** is the spend cap.

### Limits

On this machine on 2026-09-20, one signed-out preview page for `durov` held 20 posts and a 5-row run used one HTTP request. Older posts are on `?before={lowest post number}`, one request per second. That is the only volume this package has measured.

### What this does not do

- It does not log in, use a phone number, a session, or the Telegram Bot API.
- It does not read groups, member lists, comment authors, or anything about individual users.
- It does not return emails, phone numbers, or home addresses.
- It does not open private channels or channels that turned off the public preview. Those produce one error row.
- It does not invent text, views, dates, or media when the page omitted them.
- It does not solve a CAPTCHA or otherwise dodge a block.
- Telegram's terms prohibit data scraping. A 200 is not permission. See `SOURCE_TERMS.md`.

### Refunds and support

Refunds: if a run returns zero post rows for a valid public channel, email operations@ustechautomations.com within 7 days and we refund that run. Support: same address, replies within 2 business days.

# Actor input Schema

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

Public channel usernames or t.me / t.me/s/ links. Groups, bots, private channels, and member lists are not read.

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

Optional. Only posts on or after this moment (ISO date or datetime). Leave blank for the latest posts on the public preview.

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

Ceiling on posts read from one channel. Default 50, hard ceiling 1000.

## `maxItems` (type: `integer`):

Hard ceiling on rows returned, and therefore on the cost of the run. Every row bills at the listed price from row one; there is no start fee.

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

Apify Proxy. Off by default so a local run uses no proxy. Turn it on on the Store only if Telegram blocked the machine.

## Actor input object example

```json
{
  "channels": [
    "durov"
  ],
  "maxPostsPerChannel": 50,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

No description

## `csv` (type: `string`):

No description

## `report` (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"
    ],
    "maxPostsPerChannel": 50,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/telegram-channel-posts").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"],
    "maxPostsPerChannel": 50,
    "maxItems": 100,
}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usta/telegram-channel-posts"
        }
    }
}
```

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/dRnf11e6nFdoteCzJ/builds/yrNvA116XEhdWxb7t/openapi.json