Telegram Username Info Scraper
Public Telegram channel info by username or t.me URL, in typed JSON: title, verified flag, subscriber text, description, profile image, media counts and recent messages. 1 credit per call. No Telegram login.
Free API key · 1 credit per channel lookup · failed calls free
// GET /api/v2/telegram-channel/?urls=https://t.me/durov · sample from the catalog { "success": true, "data": { "urls": "https://t.me/durov", "channel": { "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" }, "next_cursor": null } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Telegram Username Info Scraper returns the public profile of a Telegram channel. Send a t.me URL or @handle and get JSON with username, title, verified, subscribers, description and a messages array of recent posts. It costs 1 credit per successful call and needs no Telegram login.
Telegram Username Info Scraper looks up one public Telegram channel and returns its profile as data. You give it a t.me URL or an @handle; it returns the channel title, username, verified flag, subscriber text, description, profile image, counts of media, videos and links, and the channel's recent messages embedded in the same record. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or load into a spreadsheet. It is one of 2 Telegram endpoints on the same API key used by 12,000+ developers.
What data can I extract with Telegram Username Info Scraper?
Using this Telegram Username Info Scraper, you can extract the following data from public Telegram channel lookups:
Want the exact field names? See the example output.
Try Telegram Username Info 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 Username Info 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 Username Info Scraper to get public Telegram channel lookups. Endpoint: GET https://proxy.scrapier.io/api/v2/telegram-channel/?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.channel: username, title, verified, subscribers, description, profile_image, url, media_count, video_count, link_count, messages, scraped_at. 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-channel" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Telegram channel lookups 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 Username Info Scraper in the catalogIt lives under Scrapers / Telegram.
- Enter the channelPut a public channel URL or @handle in
urls, such ashttps://t.me/durov. Optionally setmax_itemsfor how many messages to embed. - 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 channel comes back as JSON under
data.channel, with recent posts inmessages. Store it as is, or write it to a sheet.
How to scale to bulk Telegram channel lookups
urls takes one value per call, so for a list of channels you loop: one request per channel. 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 channel lookups cost 1,000 credits, inside the Hobby plan's 15,000.
Features
Telegram Username Info Scraper turns a public channel into one clean record you can store, compare and feed to a model. It suits community research, channel monitoring, lead lists, brand tracking and any workflow that starts from a Telegram handle, with no Telegram account to manage.
- Profile
title,username,descriptionandverifiedin one record - Audience
subscribersas the text Telegram shows - Counts
media_count,video_countandlink_count - MessagesRecent posts in
messages, with text, URL and media flags - Message count
max_itemssets how many messages are embedded (default 10) - Paging
cursorandnext_cursorfor the next page
The page fetching and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per channel lookup and 0 credits for a failed call.
Use cases
- Community researcher pulls
title,descriptionandsubscribersfor a list of channels to map a niche. - Brand monitor checks a channel's recent
messagesfor mentions of a product or competitor. - Growth analyst stores
subscribersfrom repeated calls to follow how a channel grows over time. - Lead researcher collects
descriptionand thelinksinside messages to find websites and contacts channels share. - AI engineer gives an agent a tool that looks up a handle, then asks an LLM to summarise what the channel posts about.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
The channel record and its recent messages come back together, so one request replaces a profile lookup plus a feed fetch.
It reads what any visitor to t.me sees. You never log in, manage a Telegram app or hold a session.
The same key and response envelope cover channel lookups and single posts, so a post URL from messages feeds the next call.
Input
The scraper takes one public channel per call in urls, as a t.me URL or an @handle; the aliases url, channels, usernames and username work too. Optional inputs are max_items, cursor, timeout, use_proxy and raw_data. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
urls | string | Yes | — | A public Telegram channel URL or @handle, such as https://t.me/durov. One per call. Aliases: url, channels, usernames, username. Required |
cursor | string | No | — | The next_cursor from the previous response, passed back unchanged to fetch the next page |
max_items | integer | No | 10 | Messages embedded in the channel record (default 10); above 20 triggers pagination |
timeout | integer | No | 30 | HTTP timeout in seconds, 5 to 120 (default 30) |
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 payloads under raw_responses instead of the formatted channel |
One channel per call: to look up ten channels, make ten calls. Booleans are the strings true or false, and max_items and timeout are locked into the cursor.
Example input
{
"urls": "https://t.me/durov",
"max_items": "10",
"timeout": "30",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Channel lookup data returned in data.channel | 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 channel object under channel with 13 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 payloads instead.
Example output
{
"success": true,
"data": {
"urls": "https://t.me/durov",
"channel": {
"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"
},
"next_cursor": null
}
}The catalog's sample response for urls=https://t.me/durov, labelled as a sample: live calls return the account's current values.
Channel profile
| Field | Type | Example | Description |
|---|---|---|---|
channel.username | string | "durov" | Channel handle (durov in the sample) |
channel.title | string | "Pavel Durov" | Channel display name |
channel.verified | boolean | true | true if the channel shows the verified badge |
channel.subscribers | string | "10 497 798 subscribers" | Subscriber count as Telegram's text, such as 10 497 798 subscribers |
channel.description | string | "Founder of Telegram." | The channel's description text |
channel.profile_image | string | "https://cdn4.telesco.pe/file/nQJ2NBa7Jhv9KN…" | URL of the channel's profile image |
channel.url | string | "https://t.me/durov" | Canonical t.me URL of the channel |
Content counts
| Field | Type | Example | Description |
|---|---|---|---|
channel.media_count | integer | 0 | Count of media items seen on the channel |
channel.video_count | integer | 2 | Count of videos seen on the channel |
channel.link_count | integer | 0 | Count of links seen on the channel |
Messages
| Field | Type | Example | Description |
|---|---|---|---|
channel.messages | array | 1 items | Array of recent messages: text, date, url, has_media, is_video and links |
Timestamp and input
| Field | Type | Example | Description |
|---|---|---|---|
channel.scraped_at | string | "2026-12-01T12:00:00.000Z" | When Scrapier fetched the channel |
channel.input_url | string | "https://t.me/durov" | The URL you sent |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.urls | string | "https://t.me/durov" | Your channel input, echoed back |
data.next_cursor | null | null | Cursor for the next page; null when there is no more (null in the sample) |
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 channel's t.me page, without signing in. Private channels and groups 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 Username Info 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-channel: 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-channel/ 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-channel with search_endpoints itself.
Pricing and Rate Limits
One Telegram channel lookup costs 1 credit, so 1,000 channel lookups 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 | Channel lookups included | Per 1,000 channel lookups |
|---|---|---|---|---|
| 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-channel/, 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 Username Info Scraper vs the Official Telegram API
| Feature | Scrapier channel lookup scraper | Official Telegram API |
|---|---|---|
| Access needed | One Scrapier API key | A bot token or an API ID and hash from a Telegram account |
| Public channel data | Title, subscribers text, description and recent messages in one call | Depends on the method; reading channels with a user account needs a login session |
| Fields returned | 13 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 call, 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 channel data 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 channel 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 Username Info Scraper return?
The channel object has username, title, verified, subscribers, description, profile_image, url, media_count, video_count, link_count, messages, scraped_at and input_url: 13 fields in data.channel. The data envelope adds urls and next_cursor. Each successful call costs 1 credit and needs no Telegram login.
How do I get a Telegram channel's info by username?
Send the t.me URL or @handle in urls and read data.channel. You get the title, subscriber text, description, verified flag and counts back as JSON. It works for public channels only, and each call is one channel.
Does it return the channel's messages too?
Yes. data.channel.messages holds recent posts, each with text, date, url, has_media, is_video and links. max_items sets how many are embedded, 10 by default. Above 20 the endpoint paginates: pass next_cursor back as cursor. For one post in full, use Telegram Single Post Scraper.
Why is subscribers text and not a number?
The scraper returns the subscriber figure as Telegram shows it, for example 10 497 798 subscribers. Parse the digits in your own code if you need a number. The sample date field of a message can also be empty, so check it before use.
Can I use an @handle instead of a URL?
Yes. urls accepts a public channel URL or an @handle, and the aliases url, channels, usernames and username work as well. Send one value per call: to look up several channels, loop and send one request each.
Does it work for private channels or groups?
No. Only public channels with a t.me page are returned, the same view any visitor gets without signing in. A private channel, group or invite link has no public page, so the call fails and costs 0 credits.
Does Telegram Username Info 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 channel data is returned, and no Telegram API credentials are involved.
Does Telegram Username Info 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-channel 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 channel 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 handle 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 Username Info 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 Username Info Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/telegram-channel/ with params={"urls": "https://t.me/durov"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["channel"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape Telegram channel data?
It depends on your use and your country, so this is not legal advice. Scrapier returns public channel 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 Channel Lookups
Public Telegram channel lookups as JSON, 1 credit each, from REST or MCP.