Telegram

Collect public Telegram channel profiles and messages for research, news monitoring and audience analysis. Process several channels in one run and export the results as JSON, CSV or Excel.

Features

• Get Profile: channel username, name, avatar, subscriber count, description and URL.
• Get Messages: message text, timestamps, views, available image and video links, link previews, replies and polls, together with channel details.
• Multiple channels: enter names, @handles, channel links or public post links.
• Message history: collect recent messages and page back through older posts.
• Collection controls: set page and result limits, request delay and your preferred proxy.

Example

{
  "operation": "gm",
  "profiles": ["telegram", "bloomberg"],
  "scrolltime": 1,
  "maxResults": 100,
  "delay": 3,
  "proxy": { "useApifyProxy": false }
}

Use gp for profiles or gm for messages. scrolltime controls additional pages after the initial page; 1 reads up to two pages per channel. maxResults applies across all channels. Collection stops when the requested limit or available history is reached.

Results

Profile mode returns one record per channel with username, fullname, avatar_url, followers, bio, url and an empty messages array.

Message mode returns one record per message, with the channel fields and a one-element messages array. Each message includes date, fulldate, description, image, video, preview, link, views, reply and poll. Fields unavailable in the public preview remain empty. Messages are collected newest first.

Available channels

Only channels with a public web preview are supported. Private channels, invite-only groups, personal chats and subscriber lists are unavailable. Media links are returned when present in the preview; media files are not downloaded. View and subscriber counts reflect Telegram's displayed, sometimes rounded values.

For help, open an issue and include the shared run URL and channel names.

Pay-per-event billing

Each valid pay-per-event run with at least one input includes a minimum charge of 100 result units, shared across all inputs in that run. Any placeholder rows are clearly marked and contain no scraped data; filter them out when exporting. Each separate run has its own minimum, including scheduled or API runs. Platform usage is included.

Unsuccessful lookups

Where listed in the Pricing tab, a handled lookup problem that prevents a run from returning any real results produces one clear error record and a single $0.02 unsuccessful-lookup fee, in addition to any listed start fee.