Channel research and vetting
Before you buy an ad or partner with a channel, check its subscriber count, verified flag and recent messages. Compare channels in a niche side by side.
- 1channel
- Shortlist
Public channel profiles with their recent messages, and single posts with view counts and reactions: every Telegram endpoint Scrapier ships, each returning typed JSON in the same response envelope. Public data only.
Pick the data you need. Each endpoint takes a channel or post link and gives you clean JSON back, for 1 credit per successful call.
GET/api/v2/telegram-channel/A public channel's title, description, subscriber count, verified flag and recent messages.
GET/api/v2/telegram-single-post/One channel post by URL: text, publish time, view count, reactions and media.
INusernamesWhether a Telegram username exists, if it is a user or a channel, with its title, description, photo and member count.
INkeywordsPublic emails found on Telegram pages for a keyword, with the page title, description and URL of each match.
INkeywordsPublic phone numbers on Telegram pages for a keyword and country, with the dial code, page title and URL.
Pick an endpoint, fill in the input and press Run. Without a key you see the catalog sample and nothing is billed. With your API key it runs a real call from your browser.
Every successful call costs 1 credit, whether the page holds one profile or a page of comments. Failed calls cost nothing. A free tier lets you try it first.
On Pro, 1,000 calls at 1 credit cost $1.58. Scale brings that to $1.20, so 250,000 Telegram calls a month is $299.
See all plans →| Plan | Price / mo | Credits / mo | Per 1,000 calls |
|---|---|---|---|
| Free | $0 | Free tier | — |
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Built to be easy to start with, even if you've never scraped a website. Here's how to get Telegram data in a few minutes:
https://t.me/durov, or one post link per call.telegram-channel, max_items sets how many recent messages come back with the profile.next_cursor, pass it back as cursor for the next page.X-API-Key header, or ask your AI agent over MCP.Every endpoint takes the same kind of input.
You already have the links to the pages you want.
t.me/durovt.me/durov/543// GET /api/v2/telegram-channel/ { "urls": "https://t.me/durov", "max_items": "10", "timeout": "30" }
// GET /api/v2/telegram-single-post/ { "urls": "https://t.me/durov/543" }
| Send this | Parameter | And you can get |
|---|---|---|
| Channel URL | urls | Channel title, description, subscribers, media counts and recent messages |
| Channel URL + limit | urls · max_items | The same, with up to that many recent messages |
| Post URL | urls | That post's text, publish time, views, reactions and media |
Optional on list endpoints: cursor (pass back next_cursor for the next page). Auth is one header: X-API-Key. Send parameters in the query string (GET) or as a JSON body (POST).
The one thing to know: each data type has its own shape. Field names stay the same on every call, so code and agents read them directly. Samples below come from the live catalog.
// GET /api/v2/telegram-channel/?urls=https://t.me/durov // one item of data.channel · catalog sample { "username": "durov", "title": "Pavel Durov", "verified": true, "subscribers": "10 497 798 subscribers", "description": "Founder of Telegram.", "profile_image": "https://cdn4.telesco.pe/file/nQJ2NBa7Jhv9KNN2AKCyd7OFHVjkY4U...jpg", "url": "https://t.me/durov", "media_count": 0, "video_count": 2, "link_count": 0, "messages": [ { "text": "⛔️The UK government wants to ban social media for children under 16.But banning social media for kids only puts them ...", "date": "", "url": "https://t.me/durov/528", "has_media": false, "is_video": false, "links": [] } ], "scraped_at": "2026-12-01T12:00:00.000Z", "input_url": "https://t.me/durov" }
// GET /api/v2/telegram-single-post/?urls=https://t.me/durov/543 // one item of data.post · catalog sample { "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" }
Every response is {"success": true, "data": {…}}: your input echoed back, the result under its own key (profile, posts, comments…) and next_cursor for the next page.
Public Telegram data powers channel research, market and crypto monitoring, news tracking and post performance reports. Here are four common jobs, and the Telegram scraper endpoints each one chains together.
Before you buy an ad or partner with a channel, check its subscriber count, verified flag and recent messages. Compare channels in a niche side by side.
Many projects, traders and analysts announce on Telegram first. Pull new messages from the channels you follow on a schedule, then open key posts for views and reactions.
Follow the public channels of companies, media outlets and public figures and keep every new message in one archive you can search and summarize.
Track views and reactions on your own channel's posts, or on a sponsored post you paid for, to see how each one performed over time.
Telegram Scraper fetches clean, structured data from public Telegram channels at low cost: built for channel research, monitoring and AI agents.
Each request reads Telegram at call time, and the response says when in scraped_at.
Same field names on every call, view and reaction counts as numbers, ready for code, sheets or an LLM.
One channel call returns the profile and its recent messages; max_items sets how many.
Channels and posts share the same envelope and auth as every other Scrapier platform.
The Scrapier MCP server reaches every endpoint from Claude Code, Cursor, Windsurf and VS Code with one command.
Plain REST: Python, Node.js, cURL, n8n, Make, Zapier or Google Sheets.
Public channels only. Neither live endpoint needs a Telegram account, phone number, bot or api_id.
When Telegram changes its public pages, Scrapier updates the scraper; your field names stay the same.
1 credit per call, however many messages the page holds. Failed calls are never billed.
The official Telegram Bot API only reads chats a bot has been added to, and the full Telegram API needs a user account, a phone number and an api_id. Scrapier reads any public channel or post with one API key, at a price you know before the call runs.
Any non-2xx response is free, so retries cost nothing.
At 1 credit a call. Flat per-call pricing, no compute units or bandwidth to estimate.
No bot, phone number, api_id or channel admin rights.
The same key and JSON envelope cover X, Bluesky, Threads, Reddit and more.
| Feature | Scrapier Telegram Scraper | Telegram Bot API | DIY scraper |
|---|---|---|---|
| Whose data | Any public channel | Chats the bot is added to | Any public channel |
| Setup | One API key | Bot token; an admin adds the bot | Proxies, parsers, or a user account |
| Maintenance | Handled by Scrapier | Bot updates and webhooks | Breaks on page changes |
| Cost | From $1.20 per 1,000 calls | Free | Servers and engineering time |
| AI agents | MCP server included | None | Build your own |
No. Both live Telegram endpoints read public channels and posts from their t.me links. You only need your Scrapier API key in the X-API-Key header; no phone number, bot token or api_id.
No. Scrapier reads public data only: public channels and their posts. Private groups, private channels and direct chats are not returned, and Scrapier does not join chats on your behalf.
telegram-channel returns the channel profile with its recent messages; max_items sets how many, 10 by default. When the response carries next_cursor, pass it back as cursor for the next page. Each call is 1 credit.
telegram-single-post takes a post link such as https://t.me/durov/543 and returns the text, publish time, view count as a number and as shown, each reaction with its count, the forwarded-from source and media.
The channel sample shows subscribers as Telegram prints it, for example "10 497 798 subscribers". Strip the spaces and the word to get a number. View counts on posts come back as numbers, with view_count_text beside them.
It depends on what you collect, where you are and how you use it, so this is not legal advice. Scrapier returns publicly visible data only. Some of it can be personal data under GDPR or CCPA, so collect only what you have a legitimate reason to use.
Yes. Any tool that can make an HTTP request works: n8n, Make, Zapier, Google Sheets, Airbyte or your own code. Send your key in the X-API-Key header and read the JSON response.
Yes. Run claude mcp add -t http scrapier https://mcp.scrapier.io/mcp with your key in an X-API-Key header. The agent finds the right Telegram endpoint with search_endpoints and calls it with run_scrape, in Claude Code, Cursor or Windsurf.
Check the status code first: 401 means the X-API-Key header is missing, 403 an invalid key, 402 no credits left, 429 too many requests (wait Retry-After seconds). If it's still wrong, report it with the request and the response.
Each Telegram endpoint costs 1 credit per successful call, however many messages the page holds. Failed calls are free. Plans: Hobby $29 for 15,000 credits, Pro $79 for 50,000, Scale $299 for 250,000, Enterprise custom. A free tier lets you try it first.
Run up to 3 requests in parallel per API key. If you go faster, the API answers 429 with a Retry-After header: wait that many seconds and retry. 429 and 5xx responses are never billed, and long-running endpoints need a client timeout of 210 seconds or more.
Use the requests library: requests.get("https://proxy.scrapier.io/api/v2/telegram-channel/", headers={"X-API-Key": key}, params={"urls": "https://t.me/durov"}, timeout=210). The response is JSON, so read r.json()["data"]["channel"] directly; there is no HTML to parse. Loop over your list for more channels.
Free API key. No sales call, no proxy setup, and failed calls are free.