Social Fetch
Start for freeStart free
All platforms
3 endpointsRead API docs

Telegram scraper API

Public Telegram channel metadata, post lists, and single-post lookups over REST — no userbot session.

Get 100 free credits
No credit card requiredSee pricing
99.8% uptime#3 Product of the Day3,200+ developers

Teams running monitoring, research, and enrichment pipelines

Why Social Fetch

We run the Telegram scrapers. You build the product.

Live Telegram data as JSON — proxies, platform changes and consistent output handled for you.

Telegram, plus every other network

One key and one response envelope for Telegram and 24 more platforms — profiles, posts, search, comments and transcripts.

Pricing you can reason about

One request, one credit. Know how far your balance will go before you run your next batch.

Live data on every request

Fetch public data when you ask for it — not from a shared cache.

No scraper maintenance

We handle proxies, browser changes, and platform breakages.

Built for production jobs

Run concurrent workloads with explicit statuses and request IDs.

Regular jobs. Better rates.

Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.

Never expires

What Telegram data can you get?

3 endpoints, one API key. Every response comes back as live JSON in the same envelope.

  • Profiles & channels

    Look up a Telegram account by handle or URL — bio, counts and metadata.

  • Lists & graphs

    Page through an account's posts, videos, followers and more.

  • Content

    Fetch a single post or video by URL, with metrics and media.

Browse all 3 Telegram endpoints
Use cases

What teams build with Telegram data

Monitoring, enrichment, research and content workflows on Telegram data — the same API as every other platform.

What you can build

Monitor brands and competitors

Find and vet creators

Check reach and engagement before you reach out.

Turn video into searchable text

Transcribe and index video and audio content so you can find the exact moment you need.

Track public communities

Follow the subreddits, groups, and channels where your audience talks.

Browse all workflows →

How it works

Your first request in three steps.

Use TypeScript or your automation tool of choice.

Sources

+ 19 more platforms

One request

Social Fetch API

GET/v1/tiktok/profiles/charlidamelio

x-api-key: sk_live_••••••••

1 request · 1 credit

Same JSON shape

response.json200 OK
{
  "data": {
    "lookupStatus": "found",
    "profile": {
      "platform": "tiktok",
      "handle": "charlidamelio",
      "displayName": "charli d’amelio",
      "verified": true
    },
    "metrics": {
      "followers": 160263648
    }
  }
}

  1. Step 1

    Create your free account

    Get an API key with 100 requests included.

  2. Step 2

    Choose an endpoint

    Pass a username, URL, keyword, or post ID.

  3. Step 3

    Get clean JSON

    Use the response immediately or send it into your pipeline.

Works with your stack

Code, automate, or connect your AI.

Explore integrations

Pricing

Social data, priced simply.

Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.

Starter

$29.00

18,000credits

$1.61 per 1k · $0.00161 per request

  • Top up from $1.61 / 1k if you run out
  • Up to 25 monitors
Subscribe to Starter
Most popular

Growth

$79.00

50,000credits

$1.58 per 1k · $0.00158 per request

  • Top up from $1.58 / 1k if you run out
  • 5 team seats
  • Up to 100 monitors
Subscribe to Growth

Scale

$225.00

150,000credits

$1.50 per 1k · $0.00150 per request

  • Top up from $1.50 / 1k if you run out
  • 25 team seats
  • Up to 250 monitors
Subscribe to Scale
  • Cancel anytime
  • 30-day money-back guarantee
  • Price locked while you stay

Need 1M+ credits, invoicing, or volume rates? Talk to us

Trust signals

DevHunt

Product Hunt

Uneed

Customers

Teams building on Social Fetch.

“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”

Daniel Reeve · Founder, Social Crow

  • “Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”

    Marcus Lin · Founder, Voice Gecko

  • “Live profile data on every request. We never flag accounts from a stale cache.”

    Hannah Webb · Founder, Scam Finder

  • “Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”

    Owen Pritchard · Founder, IP Flare

Telegram API: common questions

Is there a Telegram scraper API that works without a userbot?

Yes. Social Fetch Telegram routes read public channel and post data over REST. You authenticate to Social Fetch with an API key — you do not run an MTProto client session or pass Telegram user credentials.

What Telegram data does Social Fetch cover?

Public channel and group entity cards by username, recent posts for broadcast channels (with cursor pagination), and a single post by username plus numeric post id. Exact paths live under /docs/api and on this hub's endpoint list. Private chats and DMs are not covered.

Telegram Bot API vs Social Fetch — what is the difference?

Bot API is for building bots that send and receive messages inside Telegram (you need a bot token from BotFather). Social Fetch is a public-data lookup API: username or post id in, structured JSON out, no bot required. Choose Bot API when you need write access or bot interactions; choose Social Fetch for public channel enrichment and monitoring alongside other networks.

Do I need a Telegram Bot API token?

No. Social Fetch authenticates with your Social Fetch API key only. You do not pass a Bot API token for these public lookups.

Can I list posts from a public Telegram group?

No. Post list and single-post routes support public broadcast channels only. Groups are not supported on those operations. Use GET /v1/telegram/channels/{handle} when you need group metadata (title, member counts) from a public username.

How do I fetch a Telegram channel by handle?

Call GET /v1/telegram/channels/{handle} with x-api-key. The handle is the public @username (with or without @). Read data.lookupStatus before treating data.entity as found. Details are on the channel endpoint page linked below.

How do I list or fetch Telegram channel posts?

List recent messages with GET /v1/telegram/channels/{handle}/posts and page with the opaque cursor from data.nextCursor while data.hasMore is true. Fetch one message with GET /v1/telegram/channels/{handle}/posts/{postId} when you already know the numeric id from a t.me URL.

How much does the Telegram API cost?

You buy credit packs (or use the 100 free signup credits). The Telegram channel, posts list, and single-post operations document 1 credit per successful request. Check meta.creditsCharged on every response. There is no required monthly subscription for pay-as-you-go packs.

Can I read private Telegram chats or invite-only channels?

No. Only publicly visible channel and group pages. Restricted or private entities return typed lookupStatus outcomes (not_found / restricted) rather than inventing empty payloads.

Is scraping Telegram data legal?

Social Fetch returns publicly visible data. You are responsible for how you use it under Telegram's terms, applicable law, and your own compliance review. We do not give legal advice.

The Telegram API in detailHow the Telegram routes work, what they cost, and how they differ from the official API.

Why teams use Social Fetch for Telegram

Social Fetch exposes public Telegram as GET routes. Pass a public @username or post id with x-api-key and get { data, meta } with data.lookupStatus, meta.requestId, and meta.creditsCharged.

Coverage: public channel and group entity cards, broadcast-channel post lists with cursor pagination, and single-post lookups by numeric id. Private chats and DMs are out of scope. Use Bot API for sending messages or managing a bot.

How to call the Telegram API

  1. 1. Create an API key

    Sign up at Social Fetch and copy a key (sfk_…). New accounts get 100 free credits — enough to resolve one channel card and page a few posts against live data.

  2. 2. Call a Telegram route

    Start with GET /v1/telegram/channels/{handle} for the entity card, then .../posts or .../posts/{postId} when you need messages. Send x-api-key on every request. Use the playground for one-off checks; use the TypeScript SDK or curl in production jobs.

  3. 3. Read the shared envelope

    Branch on data.lookupStatus before writing rows. Log meta.requestId for support. Bill against meta.creditsCharged — that field is the source of truth for what the call cost.

What each Telegram route returns

  • Public channel and group metadata by username — title, description, avatar, verification, size fields.
  • Channel post lists (broadcast channels) with text, views, media URLs, reactions, and cursor pagination.
  • Single channel post by username and numeric post id for alerts and deep links.
  • Shared Social Fetch envelope so Telegram rows land next to other networks in one schema.

How much does the Telegram API cost?

Telegram channel, posts list, and single-post routes charge 1 credit per successful completed lookup in the OpenAPI notes. Credits never expire on pay-as-you-go packs. Always trust meta.creditsCharged on the response.

Social Fetch vs the official Telegram API

Telegram Bot API and MTProto are for bots, clients, and user-authorized apps. Social Fetch looks up public t.me pages with a Social Fetch API key only — no Bot token, no userbot session.

Pull your first Telegram data.

Run a live Telegram request in the playground. 100 free credits, no card, JSON back in seconds.

Get 100 free credits

No credit cardSign up in 30 seconds withGoogleGitHub