Telegram Channel Scraper — channels, groups & bots from t.me links

Scrape Telegram channel, group, and bot metadata straight from t.me links — display name, bio, avatar, subscriber/member counts, verified badge, and content counters. Works with public usernames AND private invite links (t.me/+...), needs no Telegram account, no API key, and no login, and returns clean JSON/CSV you can plug into any workflow.

Why use this scraper?

• Invite links supported — t.me/+hash and legacy t.me/joinchat/... links return the group/channel name, bio, avatar, and live member + online counts without joining.
• Zero setup — no Telegram API credentials, no phone number, no session files. Paste links, press Start.
• Every entity type — public channels, private groups, bots, and user profiles are auto-detected and typed (channel / group / bot / user).
• Content counters — public channels also get exact photos, videos, files, and links counts.
• Forgiving input — post URLs (t.me/channel/123), web previews (t.me/s/channel), telegram.me aliases, and bare @usernames are all normalized automatically.
• Fast and parallel — a sliding window of concurrent HTTP requests; hundreds of channels resolve in seconds.

Overview

Give the actor any list of t.me links or usernames. For each one it fetches Telegram's public preview page, detects what kind of entity it is, and returns one structured row with the name, bio, avatar URL, member counts, and (for public channels) content counters. That's it — one row in, one row out, no padding.

Supported inputs

Input	Example	Result
Public channel	https://t.me/telegram	name, bio, avatar, subscribers, photo/video/link counters
Private invite link	https://t.me/+Zt3-XNsQ5h9jYWE8	name, bio, avatar, members + online, invite hash
Legacy invite link	https://t.me/joinchat/AbCdEf123	normalized to t.me/+AbCdEf123
Bot	https://t.me/BotFather	name, bio, avatar, monthly users
User profile	https://t.me/durov	name, bio, avatar
Post URL	https://t.me/telegram/123	normalized to the channel root
Web preview	https://t.me/s/bloomberg	normalized to the channel root
Bare handle	@durov or durov (via the Usernames field)	same as the full URL

Use cases

• Channel discovery & vetting — bulk-check member counts and bios before advertising, partnering, or joining.
• Crypto / trading community intel — resolve invite links shared on social media into named, sized communities.
• Influencer & media monitoring — track subscriber growth of news channels and creators over time (schedule the actor, diff the counts).
• Lead enrichment — turn t.me links found on websites into structured channel data for your CRM.
• Trust & safety research — catalogue channel metadata at scale from lists of invite links.
• Bot market research — monthly-user counts for competing Telegram bots.

How it works

1. Normalize — every input (URL, invite link, post URL, @handle) is normalized to a canonical t.me preview URL and deduplicated.
2. Fetch — each preview page is fetched with browser-grade TLS fingerprints (impit) in a parallel sliding window. t.me has no anti-bot, so no proxy is needed.
3. Parse — display name, bio (line breaks preserved), avatar, verified badge, and counts are extracted; the entity type is detected from the page structure.
4. Enrich — for public channels, the t.me/s/ web preview adds exact photos / videos / files / links counters (toggle with channelStats).
5. Push — one dataset row per entity, JSON or CSV.

Input configuration

{
    "startUrls": [
        "https://t.me/telegram",
        "https://t.me/+Zt3-XNsQ5h9jYWE8"
    ],
    "usernames": ["@durov"],
    "channelStats": true,
    "maxItems": 1000
}

Field	Type	Default	Description
startUrls	array	—	t.me / telegram.me links — any mix of channels, groups, bots, invite links
usernames	array	[]	Bare handles as an alternative to full URLs
channelStats	boolean	true	Fetch photo/video/file/link counters for public channels (1 extra request each)
maxItems	integer	1000	Hard cap on entities scraped in the run
maxConcurrency	integer	10	Parallel requests
proxy	object	none	Optional — t.me needs no proxy; direct is fastest

Output overview

One row per Telegram entity:

{
    "url": "https://t.me/+Zt3-XNsQ5h9jYWE8",
    "username": null,
    "fullName": "SOLANA SUMMER",
    "bio": "Com : https://t.me/+Zt3-XNsQ5h9jYWE8\n\nChannel : https://t.me/Solanasummmers",
    "avatarUrl": "https://cdn4.telesco.pe/file/NFdH2M17pF...jpg",
    "memberCounts": 456,
    "type": "group",
    "subscribers": null,
    "members": 456,
    "online": 80,
    "monthlyUsers": null,
    "verified": false,
    "inviteHash": "Zt3-XNsQ5h9jYWE8",
    "scrapedAt": "2026-07-15T21:13:58.521Z"
}

Public channels additionally include:

{
    "fullName": "Telegram News",
    "username": "telegram",
    "type": "channel",
    "subscribers": 10075225,
    "memberCounts": 10075225,
    "verified": true,
    "photos": 13,
    "videos": 222,
    "files": null,
    "links": 367
}

Key output fields

Field	Description
fullName	Display name of the channel / group / bot / user
username	Public handle; null for private invite-link entities
bio	Description text with line breaks preserved
avatarUrl	Profile photo on Telegram's CDN (telesco.pe)
memberCounts	Headline count — subscribers (channels), members (groups), monthly users (bots)
type	channel / group / bot / user — auto-detected
subscribers / members / online / monthlyUsers	Granular counts; only the ones the entity exposes are set
verified	Telegram's blue-check verification badge
inviteHash	The +hash part of invite links; null for public entities
photos / videos / files / links	Content counters (public channels with channelStats: true)

FAQ

Do I need a Telegram account or API key? No. The actor reads Telegram's public t.me preview pages — no account, no api_id/api_hash, no phone number, no session string.

Does it work with private invite links? Yes — that's a headline feature. t.me/+hash links return the entity's name, bio, avatar, member count, and online count without joining. The username field is null for these because Telegram doesn't expose it pre-join.

Can it scrape channel messages/posts? No — this actor is for channel metadata. Message scraping is a different (and much heavier) problem. If you paste a post URL, the actor resolves it to the channel and returns the channel's data.

Can it search for channels by keyword? No — Telegram has no public channel search. Feed it links or usernames from your own sources (websites, social media, directories).

Are member counts exact? Yes for the headline counts — they come from the live page (e.g. 10 075 225 subscribers). The photo/video/link counters for very large channels are Telegram's own values.

What happens with dead or invalid links? Unrecognizable inputs are reported and skipped at the start; deleted/invalid entities are logged and skipped without producing a row. You only pay for actual results.

Does it expose emails or phone numbers? No — Telegram doesn't publish these on preview pages, so the actor can't (and doesn't pretend to) return them.

Support

• Issues tab — fastest way to report a problem or request a field; I typically respond within 24 hours.
• The actor sends me automatic failure alerts, so broken runs are usually being fixed before you write in.

Additional services

Need a custom pipeline (channel-growth tracking, invite-link resolution at scale, integration with your CRM), a private variant of this actor, or a scraper for another platform? Reach out via the Issues tab or my Apify profile — custom work is available.

Explore more scrapers

Check my Apify profile for more scrapers — jobs (LinkedIn, Indeed, Glassdoor, Upwork), real estate (Zillow, Realtor, Rightmove, ImmoScout24, Idealista), reviews (Trustpilot, Glassdoor), travel (Expedia), and many more directory and listing sites.

⚠️ Disclaimer

This actor collects only publicly available data from Telegram's public t.me preview pages — the same information any logged-out visitor sees in a browser. It does not access private content, does not join groups or channels, does not read messages, and does not bypass any authentication. You are responsible for how you use the data: comply with Telegram's Terms of Service, applicable data-protection laws (GDPR, CCPA), and platform policies in your jurisdiction. This actor is not affiliated with or endorsed by Telegram.

SEO Keywords

telegram channel scraper, telegram scraper, scrape telegram channel, telegram channel info, telegram members count scraper, telegram invite link resolver, t.me scraper, telegram group scraper, telegram bot scraper, telegram channel metadata, telegram subscriber count, telegram channel analytics, extract telegram channel data, telegram channel details api, telegram osint, telegram channel lookup, bulk telegram channel checker, telegram channel export, telegram data extraction, scrape t.me links