# Telegram Channel Scraper API — $0.00005/post

> Telegram channel scraper API: posts of any public channel, newest first, with text, views, date, photos, video and link previews. No account. $0.00005 per post.

[Home](https://quanticdata.io/) / [Collectors](https://quanticdata.io/collectors/) / Telegram Channel Scraper

[All collectors](https://quanticdata.io/collectors/)

# Telegram channel scraper API

Social & communities · v1.0.0 · `telegram_posts`

$0.00005 / post

$0.05 / 1K · pay per delivered post

A Telegram channel scraper API: send a channel username or t.me link and get its public posts as rows, newest first, with the text, date and views, photos, video and link previews, forwards and edits flagged. Up to 500 posts per run, no Telegram account and no API id, billed per post delivered.

By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData · Published Nov 13, 2026

[Get my free API key](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-hero) · [See the request](https://quanticdata.io/collectors/telegram-channel-scraper-api/#integration)

$0.00005 per delivered post · $2 free every month · Failed runs never billed

On this page:

- [Try it](https://quanticdata.io/collectors/telegram-channel-scraper-api/#try)
- [What it is](https://quanticdata.io/collectors/telegram-channel-scraper-api/#what)
- [Limits](https://quanticdata.io/collectors/telegram-channel-scraper-api/#caps)
- [Output fields](https://quanticdata.io/collectors/telegram-channel-scraper-api/#output)
- [Inputs](https://quanticdata.io/collectors/telegram-channel-scraper-api/#input)
- [Pricing](https://quanticdata.io/collectors/telegram-channel-scraper-api/#pricing)
- [Integration](https://quanticdata.io/collectors/telegram-channel-scraper-api/#integration)
- [Use cases](https://quanticdata.io/collectors/telegram-channel-scraper-api/#use-cases)
- [Versus the alternatives](https://quanticdata.io/collectors/telegram-channel-scraper-api/#compare)
- [FAQ](https://quanticdata.io/collectors/telegram-channel-scraper-api/#faq)

What it does

## What a Telegram channel scraper returns

Most Telegram scrapers start with a phone number: a client library logged in as a user, an API id and hash, and an account that can be limited. Public channels need none of that, because Telegram publishes them on the web. The collector reads that public view, page after page, and returns each post as a row with its views as a number, the media it carries and the link it previews.

On 13 November 2026 the latest 20 posts of the official Telegram News channel ran from 14 May to 26 August 2026, and each of them had between 1.19M and 3.14M views; 13 of the 20 carried a video. Telegram prints views rounded, so each row gives both the number, 3140000, and the label as shown, 3.14M.

## Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

| Input | Type | Required | What it does |
| --- | --- | --- | --- |
| `channel` | string | yes | Channel username or t.me link. |
| `max_results` | integer | no | How many posts to deliver at most (1–500). You pay only for delivered posts. |

Outputs — 19 fields, one row per post

## What one post looks like

Every delivered post carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

| Field | Type | What it holds |
| --- | --- | --- |
| `rank` | integer | 1-based delivery order, newest first. |
| `channel` | string | Channel username. |
| `channel_title` | string · nullable | Channel name. |
| `post_id` | integer | Id of the post in the channel. |
| `url` | string | Link to the post. |
| `text` | string · nullable | Post text, line breaks kept. |
| `created_at` | string · nullable | Posted at (ISO 8601). |
| `views` | integer · nullable | Views as a number (1.2M → 1200000; rounded by Telegram). |
| `views_label` | string · nullable | Views as Telegram prints them. |
| `edited` | boolean | True when the post was edited. |
| `author_signature` | string · nullable | Signature of the admin who posted, when the channel shows it. |
| `forwarded_from` | string · nullable | Name the post was forwarded from. |
| `photos` | string[] | Photo URLs. |
| `has_video` | boolean | True when the post carries a video. |
| `video_url` | string · nullable | Direct video link; Telegram signs it for a limited time. |
| `video_duration` | string · nullable | Video length as shown (0:06). |
| `link_url` | string · nullable | URL of the link preview. |
| `link_title` | string · nullable | Title of the link preview. |
| `link_site` | string · nullable | Site name of the link preview. |

Integration

## One POST, typed rows

Base URL `https://api.quanticdata.io/v1`, Bearer auth, the same key as every other Data API. Endpoint: `POST /v1/scraper/collectors/telegram_posts/run`.

cURL:

```bash
curl -X POST https://api.quanticdata.io/v1/scraper/collectors/telegram_posts/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"channel":"telegram","max_results":20}'
```

Python:

```python
import requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/telegram_posts/run",
    headers={"Authorization": f"Bearer {QD_API_KEY}"},
    json={
        "channel": "telegram",
        "max_results": 20
    },
    timeout=120,
)
for row in r.json()["payload"]["results"]:
    print(row)
```

Node.js:

```javascript
const res = await fetch(
  "https://api.quanticdata.io/v1/scraper/collectors/telegram_posts/run",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.QD_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({"channel":"telegram","max_results":20}),
  },
);
const { payload } = await res.json();
console.table(payload.results);
```

MCP:

```bash
claude mcp add quanticdata \
  -e QUANTICDATA_API_KEY=qd_live_your_key_here \
  -- npx -y quanticdata-mcp

# then, in the chat:
> run the telegram_posts collector with channel="telegram"
```

Example response

POST /v1/scraper/collectors/telegram_posts/run

```bash
$ curl $QD/telegram_posts/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{"channel": "telegram", "max_results": 20}'
{ "status": "done", "count": 20,
  "results": [
    {
      "post_id": "…",
      "text": "…",
      "views": "…",
      "created_at": "…" } ],
  "cost": 0.001 }
# 20 posts × $0.00005 · nothing delivered, nothing charged
```

Price

## Limits, in plain numbers

Everything that bounds one run of this collector. No hidden throttles.

Max per run

500 posts

Price

$0.00005 / post

Per 1,000

$0.05

Failed runs

Free zero rows, zero charge

Free every month

$2 no card

Rate limit

20 req/min on the free tier

Changelog

- `v1.0.0` 2026-11-11 Initial release

  A public Telegram channel's posts, about twenty per call.

Every run records the collector version it ran on. Breaking output changes bump the major version.

Try it

## Telegram channel posts, running now

Change the input and run it against the live collector — nothing to install, no sign-up.

Run it from your own code, on your own inputs

Same collector, same rows — $2 of free API credit every month, no card.

[Get my free API key](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-closing)

![Telegram channel scraper API: from channel, QuanticData reads the Telegram channel posts and returns one row per post with text, views and created_at, at $0.00005 per delivered post.](https://quanticdata.io/collectors/telegram-channel-scraper-api/diagram.webp?v=20261002s)

*You send a Telegram channel; its posts come back as rows with text, views and created_at — 19 fields on every row — and you are billed $0.00005 for each post actually delivered, nothing for a run that delivers none.*

**$0.00005 / post** · 40,000 posts on the free $2 every month

**Semantic input** · channel, max_results — no URL lists

**Up to 500** posts per run, pagination handled for you

**19 fields** · one row per post

Pricing

## Telegram Channel Scraper pricing

$0.00005 per delivered post. A run that delivers nothing costs nothing, and the $2 monthly allowance covers about 40,000 posts before you spend anything.

**$0.00005** per delivered post · *$0.05 per 1,000 delivered posts*

**40,000 posts** · on the free allowance · *$2 every month, no card*

**Zero rows** · zero charge · *a run that delivers nothing is free*

**−30%** on volume tiers · *the catalog returns your key's price*

- [Pay as you go](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-tier-1): $0/mo · $2 free credit / month · 20 requests / min (300 on real balance) · List unit prices
- [Starter](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-tier-2): $19/mo · $15 free credit / month · 300 requests / min · 10% off unit prices
- [Growth](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-tier-3): Most popular · $79/mo · $50 free credit / month · 600 requests / min · 20% off unit prices
- [Scale](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-tier-4): $299/mo · $250 free credit / month · 1,200 requests / min · 30% off unit prices

Same wallet, same key and same $2 monthly allowance as every other [Data API](https://quanticdata.io/web-data-api-for-ai/). Prices are launch pricing read live from the billing config — `GET /v1/scraper/collectors` returns the price your key actually pays.

## What people build with the Telegram channel scraper

Three shapes of work this endpoint was designed around.

### Monitoring public channels

News, crypto, gaming or brand channels read every hour: what was posted, how many views it reached, what it linked to.

### Research on open sources

Text, dates, forwards and media of public channels kept as a dataset you can search, with each channel’s size from the [Telegram channel stats API](https://quanticdata.io/collectors/telegram-channel-stats-api/).

### Measuring a placement

The views of the post that carried your ad against the channel’s usual range, read the day after and a week after.

## Telegram Channel Scraper versus rolling your own

The differences that actually cost time when you build this in-house.

|  | DIY scraper | This collector |
| --- | --- | --- |
| Access | A phone number, an API id and a logged-in client | One API key, no Telegram account |
| Views | “3.14M” to parse | A number and the label as printed |
| Media | Downloaded through the client | Photo URLs, video link and duration as fields |
| History | Your own loop over older pages | Up to 500 posts in one run, newest first |
| Forwards and edits | Read from raw message objects | `forwarded_from` and `edited` as fields |
| Billing | Your servers and your time | Only delivered posts |

![Telegram channel scraper API: the POST to the telegram_posts collector, 20 posts delivered and the bill, 20 × $0.00005 = $0.001 in usage.cost_usd; zero posts would cost $0.](https://quanticdata.io/collectors/telegram-channel-scraper-api/diagram2.webp?v=20261002s)

*The same call you would paste into a terminal: a Bearer key, the channel in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many posts arrived and usage.cost_usd is $0.001, which is 20 × $0.00005. A run that delivers nothing costs nothing.*

## Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

- [Telegram: channels FAQ](https://telegram.org/faq_channels)
- [Telegram: post widget for websites](https://core.telegram.org/widgets/post)
- [Telegram Terms of Service](https://telegram.org/tos)

## FAQ

Questions we get about the Telegram channel scraper.

[Something else? Ask us](https://quanticdata.io/collectors/telegram-channel-scraper-api/#ask)

### Can I scrape a Telegram channel without an account?

Yes, for public channels. Send the username or t.me link with your QuanticData key; no phone number, API id or session is involved. Each delivered post costs $0.00005, so 500 posts cost $0.025.

### Is there a Telegram scraper for Python?

The collector is an HTTP API, so it works from Python with requests (the Integration section has the code), and from Node.js, cURL or an MCP client. You get JSON rows, with no Telegram client library to install.

### Can I download the videos of a channel?

Each post with a video carries `video_url`, a direct link that Telegram signs for a limited time, and `video_duration`. Save the file soon after the run if you need it.

### Is it legal to scrape Telegram channels?

The collector reads only public channels, from the web view Telegram serves to anyone. How you may use the posts depends on Telegram’s Terms of Service and on the law where you work, so check both for your use case.

### Is there a free Telegram channel scraper?

Every account gets $2 of credit every month with no card, which is about 40,000 delivered posts on this endpoint at $0.00005 each. It renews monthly, and a run that delivers nothing is never billed.

### How much does one run cost?

Multiply the rows you actually receive by $0.00005. A run capped at 500 posts — the maximum for this collector — costs $0.025 if every row comes back, and less when the listing has fewer. Volume tiers take up to 30% off, and `GET /v1/scraper/collectors` returns the price your key actually pays.

## Run the Telegram channel scraper now

$2 of free credit every month, no card. Your key returns its own prices from `GET /v1/scraper/collectors`.

[Get my free API key](https://app.quanticdata.io/register?utm_source=collector-page&utm_medium=website&utm_campaign=data-api&utm_content=telegram-channel-scraper-api-cta-3)

![Illustration: three coloured zones of the page that is read (Telegram channel posts) turn into clean JSON with the fields text, views and created_at; 19 fields on every row.](https://quanticdata.io/collectors/telegram-channel-scraper-api/hero.webp?v=20261003c1)

Related:

- [All 100+ collectors](https://quanticdata.io/collectors/)
- [Telegram channel stats API](https://quanticdata.io/collectors/telegram-channel-stats-api/)
- [YouTube channel scraper API](https://quanticdata.io/collectors/youtube-channel-scraper-api/)
- [Reddit scraper API](https://quanticdata.io/collectors/reddit-scraper-api/)
- [Documentation](https://quanticdata.io/docs/)

---

Source: https://quanticdata.io/collectors/telegram-channel-scraper-api/ · Site index for AI: https://quanticdata.io/llms.txt
