New: the Scrapier MCP server. Every scraper in Claude Code with one command. See how →
GET/api/v2/telegram-single-post/

Telegram Single Post Scraper API

Last updated: · 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
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.

No key? Run the catalog sample.
ReadyLatency —Credits billed: 0
Request readyGET /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 PostmanOpenAPI spec

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.

FieldTypeExampleDescription
post.idstring"543"ID of the post within the channel (543 in the sample)
post.urlstring"https://t.me/durov/543"Canonical t.me URL of the post
post.textstring"Telegram has applied for the .gram domain z…"The post's text
post.published_atstring"2026-08-18T17:37:31+00:00"When the post was published, as an ISO timestamp
post.view_countinteger3600000Views as a number (3,600,000 in the sample)
post.view_count_textstring"3.6M"Views as Telegram shows them (3.6M in the sample)
post.reactionsarray1 itemsArray of reactions: emoji, emoji_id, count and count_text
post.reaction_countinteger111800Total reactions on the post
post.channel_handlestring"durov"Handle of the channel that posted it (durov in the sample)
post.author_namestring"Pavel Durov"Display name of the channel or author
post.author_urlstring"https://t.me/durov"t.me URL of the author
post.forwarded_fromnullnullSource of a forwarded post; null in the sample
post.mediaarray[]Array of attached media; empty in the sample
post.link_previewnullnullLink preview card if the post has one; null in the sample
post.successbooleantruetrue when the post was read
post.input_urlstring"https://t.me/durov/543"The URL you sent
post.scraped_atstring"2026-09-24T13:45:36.376Z"When Scrapier fetched the post
successbooleantruetrue on every 200 response
data.urlsstring"https://t.me/durov/543"Your post URL, echoed back
data.next_cursornullnullNull: this is a lookup with no paging
Parameters

Request Parameters Reference

NameTypeRequiredDefaultDescriptionExample
urlsstringYes—A public Telegram post URL, such as https://t.me/durov/543. One per call. Alias: url. Requiredhttps://t.me/durov/543
cursorstringNo—The next_cursor from a previous response; this lookup always returns null, so you rarely need it—
use_proxybooleanNotrueUse Scrapier's residential proxy pool when true (default true). Leave as istrue
raw_databooleanNofalseReturn the raw upstream payload under raw_responses instead of the formatted posttrue

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

MetricValueSource
Cost of a successful call1 creditScrapier catalog
Cost of a failed call0 creditsAny non-2xx response
Parallel requests per key3Above that: 429 with Retry-After
Recommended client timeout210 secondsScrapier 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.

FeatureScrapier post scraperOfficial Telegram API
Access neededOne Scrapier API keyA bot token or an API ID and hash from a Telegram account
Post views and reactionsView count and each reaction count in one callDepends on the method and on your access to the channel
Fields returned17 fields in one typed recordObjects and methods defined by the Telegram API
Rate limitsUp to 3 parallel requests per key; 429 with Retry-AfterFlood limits set by Telegram
SetupSign up, copy a key, send a requestRegister an app, authorise a session, write client code
Cost1 credit per post, from $1.20 per 1,000 callsFree to call; you run the client and the account
Errors

Errors and Retry Handling

StatusMeaningBilledFix
200Post data returned in data.postYes—
400Bad or missing inputNoCheck urls: one value per call
401X-API-Key header missingNoAdd the header
402Out of credits (body has balance)NoTop up; retrying will not help
403Invalid or revoked API keyNoCheck the key in your dashboard
429ThrottledNoWait Retry-After seconds, then retry
5xxUpstream failure or timeoutNoRetry with backoff; set a 210 s client timeout

From the error reference. 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

PlanMonthly pricePosts includedCost per 1,000
Hobby$2915,000$1.93
Pro$7950,000$1.58
Scale$299250,000$1.20

See all plans →

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.

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.

Analysts

CSV and flattened JSON

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

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.

Fetch public Telegram posts as typed JSON in one request

1 credit per post · failed calls free