Telegram Single Post Scraper
One public Telegram post by t.me URL, in typed JSON: text, publish time, view count, reactions, media, forwarded-from and link preview. 1 credit per call. No Telegram login.
Free API key · 1 credit per post · failed calls free
// GET /api/v2/telegram-single-post/?urls=https://t.me/durov/543 · sample from the catalog { "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 }, "next_cursor": null } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Telegram Single Post Scraper returns one public Telegram post. Send a t.me post URL and get JSON with text, published_at, view_count, reactions, reaction_count, media and author_name. It costs 1 credit per successful call and needs no Telegram login.
Telegram Single Post Scraper reads one public post from a Telegram channel and returns it as data. You give it a post URL such as https://t.me/durov/543; it returns the text, publish time, view count, each reaction with its count, the media, any forwarded-from source and a link preview, plus the channel handle and author. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or load into a dashboard. It is one of 2 Telegram endpoints on the same API key used by 12,000+ developers, and it pairs with the channel lookup that lists post URLs.
What data can I extract with Telegram Single Post Scraper?
Using this Telegram Single Post Scraper, you can extract the following data from public Telegram posts:
Want the exact field names? See the example output.
Try Telegram Single Post Scraper Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use Telegram Single Post Scraper
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier Telegram Single Post Scraper to get public Telegram posts. Endpoint: GET https://proxy.scrapier.io/api/v2/telegram-single-post/?urls={urls} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in urls; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.post: input_url, success, id, channel_handle, url, author_name, author_url, text, published_at, view_count, view_count_text, reactions. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "telegram-single-post" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Telegram posts on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open Telegram Single Post Scraper in the catalogIt lives under Scrapers / Telegram.
- Enter the post URLPut the public t.me post URL in
urls, such ashttps://t.me/durov/543. The aliasurlworks too. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. Keep a 210-second client timeout. - Save your resultsThe post comes back as JSON under
data.post, withview_countandreactionsbeside the text. Store it as is, or write it to a sheet.
How to scale to bulk Telegram posts
urls takes one value per call, so for a list of posts you loop: one request per post. There is no paging: data.next_cursor is null. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each call is 1 credit and failed calls are free, so 1,000 posts cost 1,000 credits, inside the Hobby plan's 15,000.
Features
Telegram Single Post Scraper turns one t.me post into a record you can store, compare and feed to a model. It suits engagement tracking, content archiving, research and any workflow that needs the exact text, views and reactions of a known post.
- Text
textholds the post's text - Views
view_countas a number andview_count_textas shown - Reactions
reactionswith emoji and count, plusreaction_count - Timing
published_atas an ISO timestamp - Media
mediaandlink_previewfor attached content - Source
forwarded_fromwhen the post was forwarded
The page fetching and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per post and 0 credits for a failed call.
Use cases
- Engagement analyst re-fetches a post over time and compares
view_countandreaction_countto see how it spreads. - Researcher archives the
textandpublished_atof cited posts so a study keeps the evidence. - Brand monitor checks the reactions and views of a post that mentions a product.
- Journalist verifies the author, publish time and forwarded-from source of a post before quoting it.
- AI engineer gives an agent a tool that fetches a post URL, then asks an LLM to summarise or translate the text.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
You send the post URL and get its views and each reaction count, not a feed you have to search.
It reads what any visitor to the post's t.me page sees. You never log in, manage a Telegram app or hold a session.
The same key and response envelope cover posts and channel lookups, so post URLs from a channel's messages feed this call.
Input
The scraper takes one public Telegram post URL per call in urls, such as https://t.me/durov/543; the alias url works too. Optional inputs are cursor, use_proxy and raw_data. It is a lookup: next_cursor is null. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
urls | string | Yes | — | A public Telegram post URL, such as https://t.me/durov/543. One per call. Alias: url. Required |
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 |
raw_data | boolean | No | false | Return the raw upstream payload under raw_responses instead of the formatted post |
One post per call: to fetch ten posts, make ten calls. Booleans are the strings true or false.
Example input
{
"urls": "https://t.me/durov/543",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| 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. Any non-2xx response costs 0 credits.
Output
Typed JSON with the same schema on every call. One call returns one post object under post with 17 fields, inside the standard data envelope. data also carries your urls input and next_cursor. Field names stay the same on every call. Set raw_data to true if you want Telegram's raw page payload instead.
Example output
{
"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
}
}The catalog's sample response for urls=https://t.me/durov/543, labelled as a sample: live calls return the account's current values.
Post
| 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 |
Reach and reactions
| Field | Type | Example | Description |
|---|---|---|---|
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 |
Channel and author
| Field | Type | Example | Description |
|---|---|---|---|
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 |
Attachments
| Field | Type | Example | Description |
|---|---|---|---|
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 |
Status and input
| Field | Type | Example | Description |
|---|---|---|---|
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 |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
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 |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of Telegram's pages happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: what any visitor sees on a public post's t.me page, without signing in. Posts in private channels are out of reach.
The schema is stable. When Telegram changes its pages, Scrapier updates the scraper and the field names stay the same.
How do you integrate Telegram Single Post Scraper into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including telegram-single-post: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/telegram-single-post/ with the input as a query parameter. Map data into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map the fields you need straight into Sheets, Airtable or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds telegram-single-post with search_endpoints itself.
Pricing and Rate Limits
One Telegram post costs 1 credit, so 1,000 posts cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Posts included | Per 1,000 posts |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /telegram-single-post/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
Telegram Single Post Scraper vs the Official Telegram API
| 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 |
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.
Is it legal to scrape Telegram data?
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.
Frequently asked questions
What fields does Telegram Single Post Scraper return?
The post object has id, url, text, published_at, view_count, view_count_text, reactions, reaction_count, channel_handle, author_name, author_url, forwarded_from, media, link_preview, success, input_url and scraped_at: 17 fields in data.post. Each successful call costs 1 credit and needs no Telegram login.
How do I scrape a single Telegram post?
Send the public post URL, such as https://t.me/durov/543, in urls and read data.post. You get the text, publish time, views and reactions as JSON. Each call is one post, and it works for public channels only.
Does it return view counts and reactions?
Yes. view_count is a number and view_count_text is the figure as Telegram shows it, such as 3.6M. reactions lists each emoji with count and count_text, and reaction_count is the total across all reactions.
Where do I find post URLs to send?
Use the t.me link of any public post. To list a channel's recent posts first, call Telegram Username Info Scraper: data.channel.messages has a url for each message, and you can send those to this endpoint for full detail.
What do media, forwarded_from and link_preview hold?
media is an array of attached items, forwarded_from names the source of a forwarded post and link_preview is the card for a shared link. In the catalog sample, media is empty and the other two are null, so check for empty values in your code.
Does it work for posts in private channels?
No. Only posts with a public t.me page are returned, the same view any visitor gets without signing in. A post in a private channel or group has no public page, so the call fails and costs 0 credits.
Does Telegram Single Post Scraper require a Telegram account or login?
No. It uses no Telegram account, bot token or session: you send your Scrapier API key in the X-API-Key header and the input, and get JSON back. Only public post data is returned, and no Telegram API credentials are involved.
Does Telegram Single Post Scraper work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds telegram-single-post with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
What happens if the URL is wrong or Telegram returns nothing?
If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that URL or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.
Does it return data in a format LLMs can use directly?
Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.
How much does it cost to run Telegram Single Post Scraper 1,000 times?
1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I use Telegram Single Post Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/telegram-single-post/ with params={"urls": "https://t.me/durov/543"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["post"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape Telegram posts?
It depends on your use and your country, so this is not legal advice. Scrapier returns public post data only. Telegram's terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping Telegram Posts
Public Telegram posts as JSON, 1 credit each, from REST or MCP.