# Telegram Single Post Scraper REST API Docs | Scrapier (https://scrapier.io/scrapers/telegram/post/api/)

> Call the Telegram Single Post Scraper REST API from cURL, Python or Node.js. One GET, one header, typed JSON back. 1 credit per post. Failed calls free.

Last updated: 2026-11-11

**GET**/api/v2/telegram-single-post/

## Telegram Single Post Scraper _API_

Last updated: 9 Nov 2026 · REST · JSON

Quick answer

Send `GET https://proxy.scrapier.io/api/v2/telegram-single-post/?urls=https://t.me/durov/543` with your key in the `X-API-Key` header. You get the post back as JSON. 1 credit per post; failed calls are free.

- 1 credit per post
- Failed calls free
- 3 parallel requests per key

[Get a free API key →](https://app.scrapier.io/sign-up)[Jump to the playground](#playground)

Copy for your AI agent

API

## Call the Telegram Single Post Scraper API

Use the Telegram Single Post Scraper API from your own apps, scripts or agents. You need a Scrapier account and the API key from your dashboard. Pick a language.

post.py

import requests\# Replace YOUR\_API\_KEY with the key from your Scrapier dashboardAPI\_KEY = "YOUR\_API\_KEY"params = {    "urls": "https://t.me/durov/543",}r = requests.get(    "https://proxy.scrapier.io/api/v2/telegram-single-post/",    headers={"X-API-Key": API\_KEY},    params=params,    timeout=210,)r.raise\_for\_status()\# The result sits under data.postresult = r.json()\["data"\]\["post"\]print(result)

### Telegram Single Post Scraper API in Python

Plain `requests` is all you need — no SDK. Every response is typed JSON.

Install

**$** pip install requests

Other ways to call it

Playground

## Telegram Single Post Scraper API Interactive Playground

Edit the request, watch the code update, then run it. Without a key it shows the catalog sample and bills nothing. With your key it makes a real call from your browser; the key goes only to proxy.scrapier.io and is never stored.

ReadyLatency **—**Credits billed: **0**

Request ready`GET /api/v2/telegram-single-post/?urls=https://t.me/durov/543`

Press **Run request** to send it. Without a key you get the catalog sample.

Sending request…

**Error**

Failed calls are not billed.

[Import in Postman](https://docs.scrapier.io/integrations/openapi.md)[OpenAPI spec](https://proxy.scrapier.io/api/v2/openapi.json)

The sample is the same for every input: it shows the response shape, not the account you typed.

### Example response, catalog sample from 9 Nov 2026

{
  "success": true,
  "data": {
    "urls": "https://t.me/durov/543",
    "post": {
      "input\_url": "https://t.me/durov/543",
      "success": true,
      "id": "543",
      "channel\_handle": "durov",
      "url": "https://t.me/durov/543",
      "author\_name": "Pavel Durov",
      "author\_url": "https://t.me/durov",
      "text": "Telegram has applied for the .gram domain zone...",
      "published\_at": "2026-08-18T17:37:31+00:00",
      "view\_count": 3600000,
      "view\_count\_text": "3.6M",
      "reactions": \[
        {
          "emoji": "⭐",
          "emoji\_id": null,
          "count": 17300,
          "count\_text": "17.3K"
        }
      \],
      "reaction\_count": 111800,
      "forwarded\_from": null,
      "media": \[\],
      "link\_preview": null,
      "scraped\_at": "2026-09-24T13:45:36.376Z"
    },
    "next\_cursor": null
  }
}

Data

## Data You Can Extract

Telegram Single Post Scraper reads one public post from a Telegram channel and returns it as data. Every field below comes from the catalog sample response, as typed JSON.

Post

4 fields in the response.

- id
- url
- text
- published\_at

Reach and reactions

4 fields in the response.

- view\_count
- view\_count\_text
- reactions
- reaction\_count

Channel and author

4 fields in the response.

- channel\_handle
- author\_name
- author\_url
- forwarded\_from

Attachments

2 fields in the response.

- media
- link\_preview

Status and input

3 fields in the response.

- success
- input\_url
- scraped\_at

Response envelope and paging

3 fields in the response.

- success
- data.urls
- data.next\_cursor

Schema

## Response Schema Reference

Every field in the sample response. Field names stay the same on every call.

| Field | Type | Example | Description |
| --- | --- | --- | --- |
| `post.id` | string | `"543"` | ID of the post within the channel (543 in the sample) |
| `post.url` | string | `"https://t.me/durov/543"` | Canonical t.me URL of the post |
| `post.text` | string | `"Telegram has applied for the .gram domain z…"` | The post's text |
| `post.published_at` | string | `"2026-08-18T17:37:31+00:00"` | When the post was published, as an ISO timestamp |
| `post.view_count` | integer | `3600000` | Views as a number (3,600,000 in the sample) |
| `post.view_count_text` | string | `"3.6M"` | Views as Telegram shows them (3.6M in the sample) |
| `post.reactions` | array | `1 items` | Array of reactions: emoji, emoji\_id, count and count\_text |
| `post.reaction_count` | integer | `111800` | Total reactions on the post |
| `post.channel_handle` | string | `"durov"` | Handle of the channel that posted it (durov in the sample) |
| `post.author_name` | string | `"Pavel Durov"` | Display name of the channel or author |
| `post.author_url` | string | `"https://t.me/durov"` | t.me URL of the author |
| `post.forwarded_from` | null | `null` | Source of a forwarded post; null in the sample |
| `post.media` | array | `[]` | Array of attached media; empty in the sample |
| `post.link_preview` | null | `null` | Link preview card if the post has one; null in the sample |
| `post.success` | boolean | `true` | true when the post was read |
| `post.input_url` | string | `"https://t.me/durov/543"` | The URL you sent |
| `post.scraped_at` | string | `"2026-09-24T13:45:36.376Z"` | When Scrapier fetched the post |
| `success` | boolean | `true` | true on every 200 response |
| `data.urls` | string | `"https://t.me/durov/543"` | Your post URL, echoed back |
| `data.next_cursor` | null | `null` | Null: this is a lookup with no paging |

Parameters

## Request Parameters Reference

| Name | Type | Required | Default | Description | Example |
| --- | --- | --- | --- | --- | --- |
| `urls` | string | Yes | — | A public Telegram post URL, such as `https://t.me/durov/543`. One per call. Alias: `url`. Required | `https://t.me/durov/543` |
| `cursor` | string | No | — | The `next_cursor` from a previous response; this lookup always returns null, so you rarely need it | — |
| `use_proxy` | boolean | No | `true` | Use Scrapier's residential proxy pool when true (default true). Leave as is | `true` |
| `raw_data` | boolean | No | `false` | Return the raw upstream payload under `raw_responses` instead of the formatted post | `true` |

One post per call: to fetch ten posts, make ten calls. Booleans are the strings `true` or `false`.

### Pagination in the Telegram Single Post Scraper API

The Telegram Single Post Scraper API is a single lookup: one call returns the whole result and there is no `cursor` to page through. A successful call costs 1 credit; failed calls cost 0.

Access

## Access Without Telegram Login

The Telegram Single Post Scraper API needs no Telegram account, no login and no session cookies. You send your Scrapier key in the `X-API-Key` header and get JSON back. It reads public data only: what any visitor sees without logging in.

Performance

## Speed, Cost and Concurrency

| Metric | Value | Source |
| --- | --- | --- |
| Cost of a successful call | 1 credit | Scrapier catalog |
| Cost of a failed call | 0 credits | Any non-2xx response |
| Parallel requests per key | 3 | Above that: `429` with `Retry-After` |
| Recommended client timeout | 210 seconds | Scrapier docs, every endpoint |

### Latency of the Telegram Single Post Scraper API

Scrapier does not publish a latency or success-rate figure for this endpoint. Each call reads Telegram at call time, so response time depends on Telegram and on the size of the result. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.

Limits

## Limits of the Endpoint

Honest constraints of the Telegram Single Post Scraper API.

- Public data only.
- A failed call, for example a missing or unavailable post, returns a non-2xx status and costs 0 credits.
- Data is read live at call time.
- 3 parallel requests per key; above that the API answers `429` with `Retry-After`.
- Fields Telegram does not show are not returned.

Compare

## Scrapier vs the Official Telegram API

The official Telegram API is the better choice when you build a bot, send messages or need data only a signed-in member can see.

| Feature | Scrapier post scraper | Official Telegram API |
| --- | --- | --- |
| Access needed | One Scrapier API key | A bot token or an API ID and hash from a Telegram account |
| Post views and reactions | View count and each reaction count in one call | Depends on the method and on your access to the channel |
| Fields returned | 17 fields in one typed record | Objects and methods defined by the Telegram API |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Flood limits set by Telegram |
| Setup | Sign up, copy a key, send a request | Register an app, authorise a session, write client code |
| Cost | 1 credit per post, from $1.20 per 1,000 calls | Free to call; you run the client and the account |

Errors

## Errors and Retry Handling

| Status | Meaning | Billed | Fix |
| --- | --- | --- | --- |
| 200 | Post data returned in `data.post` | Yes | — |
| 400 | Bad or missing input | No | Check `urls`: one value per call |
| 401 | `X-API-Key` header missing | No | Add the header |
| 402 | Out of credits (body has `balance`) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait `Retry-After` seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |

From the [error reference](https://docs.scrapier.io/errors/). Any non-2xx response costs 0 credits.

### Retry logic for the Telegram Single Post Scraper API

retry.py

import time, requests

def get\_post(value, key, tries=5):
    for attempt in range(tries):
        r = requests.get(
            "https://proxy.scrapier.io/api/v2/telegram-single-post/",
            headers={"X-API-Key": key},
            params={"urls": value},
            timeout=210,
        )
        if r.status\_code == 429:
            time.sleep(int(r.headers.get("Retry-After", 2 \*\* attempt)))
        elif r.status\_code >= 500:
            time.sleep(2 \*\* attempt)
        else:
            r.raise\_for\_status()
            return r.json()
    raise RuntimeError("gave up after retries")

Pricing

## Pricing and Rate Limits

| Plan | Monthly price | Posts included | Cost per 1,000 |
| --- | --- | --- | --- |
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |

[See all plans →](https://scrapier.io/pricing/)

### Billing rules for the Telegram Single Post Scraper API

The Telegram Single Post Scraper API bills 1 credit per successful post. Failed calls, meaning any non-2xx status, cost 0 credits. Every plan allows 3 parallel requests per key. The free tier lets you try it before you pay.

Bulk

## Bulk Lookups and CSV

`urls` takes one value per call. For a list, loop and run up to 3 requests in parallel per key, then flatten each row into one CSV line.

bulk.py

import csv, requests
from concurrent.futures import ThreadPoolExecutor

values = \["https://t.me/durov/543"\]  \# your list

def fetch(value):
    r = requests.get(
        "https://proxy.scrapier.io/api/v2/telegram-single-post/",
        headers={"X-API-Key": "YOUR\_API\_KEY"},
        params={"urls": value},
        timeout=210,
    )
    r.raise\_for\_status()
    out = r.json()\["data"\]\["post"\]
    return out if isinstance(out, list) else \[out\]

\# 3 parallel requests per key is the limit
with ThreadPoolExecutor(max\_workers=3) as pool:
    rows = \[row for part in pool.map(fetch, values) for row in part\]

cols = \["id", "channel\_handle", "author\_name", "published\_at", "view\_count", "view\_count\_text"\]
with open("out.csv", "w", newline="") as f:
    w = csv.DictWriter(f, fieldnames=cols, extrasaction="ignore")
    w.writeheader()
    w.writerows(rows)

### CSV export from the Telegram Single Post Scraper API

out.csvcatalog sample · 1 row

id,channel\_handle,author\_name,published\_at,view\_count,view\_count\_text
543,durov,Pavel Durov,2026-08-18T17:37:31+00:00,3600000,3.6M

Agents

## AI Agent Access via MCP

### MCP for the Telegram Single Post Scraper API

The same endpoint is available to AI agents through the Scrapier MCP server at `https://mcp.scrapier.io/mcp`. One command registers it in Claude Code: `claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"`. The agent finds the endpoint with `search_endpoints` and calls it with `run_scrape` and the endpoint id `telegram-single-post`. It takes the same `urls` input and costs the same 1 credit per post. Setup for every client is on the [Telegram Single Post Scraper MCP page](https://scrapier.io/scrapers/telegram/post/mcp/).

Integrations

## Integration Paths by Role

No-code

### n8n and Make

1. Add an HTTP Request step
2. GET the endpoint with your `X-API-Key` header
3. Map the `data.post` fields to your columns

Developers

### Loop and paginate

for value in values: rows += get(value)

AI agents

### MCP tool in your agent

Call `run_scrape` with endpoint `telegram-single-post` from Claude, Cursor or Windsurf. Setup is on the [MCP page](https://scrapier.io/scrapers/telegram/post/mcp/).

Analysts

### CSV and flattened JSON

Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.

Legal

## Legal and Compliance Notes

Scraping publicly available Telegram posts is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only what any visitor sees on a public post page, with no login. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data, such as names, handles or messages, must still comply with local data-protection rules, and Telegram's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our [Terms of Use](https://scrapier.io/terms/).

FAQ

## Frequently Asked Questions

### Is there a Telegram post API?

Yes. Scrapier's Telegram Single Post Scraper API returns any public post as JSON with one GET request and an X-API-Key header. No Telegram app or login.

### How do I call it from Python?

Use \<code>requests.get\</code> on \<code>https://proxy.scrapier.io/api/v2/telegram-single-post/\</code> with \<code>params={'urls': 'https://t.me/durov/543'}\</code> and \<code>headers={"X-API-Key": KEY}\</code>. Read \<code>r.json()\["data"\]\["post"\]\</code>.

### What happens when a call fails?

Any non-200 response is free. Retry 429 and 5xx with backoff; the API already retries upstream failures.

### How much does it cost?

1 credit per successful call — about $1.58 per 1,000 posts on the Pro plan. Failed calls are free.

### Is there an OpenAPI spec?

Yes. It needs no key and covers every Scrapier endpoint.

Related

## Related Telegram APIs

[### Channel Profile + Messages API

A public channel's title, description, subscriber count, verified flag and recent messages.](https://scrapier.io/scrapers/telegram/channel/)[### All Telegram APIs

All 2 Telegram endpoints.](https://scrapier.io/scrapers/telegram/)

## Fetch public Telegram posts as typed JSON in one request

1 credit per post · failed calls free

[Get a free API key →](https://app.scrapier.io/sign-up)

---
Canonical page: https://scrapier.io/scrapers/telegram/post/api/
Site index for AI agents: https://scrapier.io/llms.txt
