Telegram API Documentation

Retrieve public Telegram channel and group profiles, channel posts, and individual public post metadata as structured JSON. 4 endpoints documented below.

Try Get a public Telegram channel profile Start with endpoint docs Pricing

First request

Endpoint: GET /telegram/channel
Cost: 2 credits/request

curl -X GET "https://api.crawlora.net/api/v1/telegram/channel?username=durov" \
  -H "x-api-key: $CRAWLORA_API_KEY"

API key authentication Error handling guide Rate limits and credits Telegram Public Channel API

How to use Telegram endpoints

Crawlora's 4 Telegram endpoints cover public channel and group profiles and public channel posts. A pull of @telegram on 2026-10-27 shows how the data behaves: 9,239,233 subscribers reported as exact, 16 photos, 228 videos and 378 links in the profile counters, and a first page of 20 posts that spans only four dates because Telegram announces features in bursts. Views arrive rounded and post links include sibling links. Private messages, private groups and account data are outside this API surface, and the endpoint documentation says results must not be used to train AI or machine-learning systems.

Step 1
Size a channel before reading it
/telegram/channel with a public username (with or without @, or a t.me link) returns title, description, verification badge, subscriber count and photo, video, file and link counters. For @telegram on 2026-10-27, subscribers_approximate was false, so 9,239,233 is an exact figure, and files_count was 0 while videos_count was 228. Check that flag before comparing channels.
Step 2
Page backwards with next_before
/telegram/channel-posts returns 20 posts per page, newest first. The first page ran from post 460 down to 441 and returned next_before 441 with has_more true; pass it as before for the next older page. A query term searches inside the channel, and a search with no matches returns an empty list, not an error.
Step 3
Group posts into bursts before counting them
Those 20 posts fall on four days: 6 posts on 2026-08-26 (ids 455 to 460, published within about 90 seconds), 5 on 2026-07-19, 4 on 2026-06-18 and 5 on 2026-05-14. Each is a feature drop, with a summary post linking the blog. Count by publish day, not by post, if you want a cadence, and note that the newest post on 2026-10-27 was still the one from 2026-08-26.
Step 4
Treat views as rounded and links as noisy
Views came back as round numbers such as 2,120,000 and 1,040,000, so differences below roughly ten thousand are not meaningful. The links array on a post also lists sibling posts in the same burst (t.me/telegram/455 to 460), so drop links that point back to the channel when you want outbound references. A post can be marked edited, as post 455 was.
Step 5
Look up one post by id
Pass the username and a post id from the listing to /telegram/post. Keep the returned source identity and retrieval time with the record, because views and reactions keep changing.
Step 6
Use the group route only for groups
/telegram/group resolves public groups. The channel route does not support private channels, groups, bots or user accounts, and returns an error naming which kind of name you passed, which is a cheap way to classify an unknown username.

Telegram API endpoints

GET/telegram/channel-postsapiKey1 credit/request

List posts from a public Telegram channel

Returns one page of up to 20 posts from a public Telegram channel's web preview (t.me/s/{username}), newest first. Each post has its id, link, text, links found in the text, publish time, edited flag, view count, author signature, forwarded-from and reply references, photo and video thumbnails, link-preview card, and reaction tallies. Page backwards by passing the previous response's next_before as before; has_more is false and next_before is omitted on the last page. Pass query to search inside the channel instead of browsing; search pages use the same before cursor. A search with no matches returns an empty posts list. Views are the preview's abbreviated figures (for example 32.4K) and are approximate above 1,000. Media entries carry thumbnail references only, never playable file URLs. Polls, documents, voice notes and stickers appear as an unsupported media entry. Private channels, groups, bots, user accounts and channels that disabled their web preview are not supported. Telegram's terms restrict using platform content to train AI or machine-learning systems, so results must not be used for that purpose.

Required: username. Optional: before, query.

Open in Playground

GET/telegram/channelapiKey2 credits/request

Get a public Telegram channel profile

Returns the public profile of a Telegram channel: title, description, verification badge, subscriber count, and the photo, video, file and link counters shown on the channel's public web preview (t.me/s/{username}). username is the channel's public username, with or without a leading @ or a t.me link; private channels, groups, bots, user accounts and invite links are not supported and return an error that says which kind of name was given. subscribers is the exact figure when available; subscribers_approximate is true when only the preview's abbreviated figure (for example 10.3M) could be read. The photo, video, file and link counters are the preview's abbreviated figures and are approximate for large channels. Only public content is read, no media files are returned, and Telegram's terms restrict using platform content to train AI or machine-learning systems, so results must not be used for that purpose.

Required: username.

Open in Playground

GET/telegram/groupapiKey1 credit/request

Get a public Telegram group profile

Returns the public profile of a Telegram group from its public t.me page: title, description, member count and, when Telegram shows it, the number of members online. username is the group's public username, with or without a leading @ or a t.me link. Only the profile is available for groups; their messages are not readable here. Channels (use telegram-channel), bots, user accounts and invite links are not supported and return an error that says which kind of name was given; a username nobody owns returns not found. online is 0 when Telegram shows no online figure. avatar_url is omitted for groups without a profile photo. Only public content is read, and Telegram's terms restrict using platform content to train AI or machine-learning systems, so results must not be used for that purpose.

Required: username.

Open in Playground

GET/telegram/postapiKey1 credit/request

Get one public Telegram channel post

Returns a single post from a public Telegram channel by username and post id, as Telegram's public embed widget shows it: text, links, publish time, edited flag, views, author signature, forwarded-from and reply references, photo and video thumbnails, link-preview card, and reaction tallies. The post id is the number at the end of a post link (t.me/durov/531 has id 531) or the id field of telegram-channel-posts. A post that does not exist, was deleted, or belongs to a channel that is not public returns not found. Telegram's terms restrict using platform content to train AI or machine-learning systems, so results must not be used for that purpose.

Required: username, id.

Open in Playground

Other Social & Creator Platforms APIs

YouTube API Twitch API TikTok API Instagram API All platforms

Back to docs

Docs menu

API Reference

Telegram API Documentation

Retrieve public Telegram channel and group profiles, channel posts, and individual public post metadata as structured JSON. 4 endpoints documented below.

Try Get a public Telegram channel profile Start with endpoint docs Pricing

First request

Endpoint: GET /telegram/channel
Cost: 2 credits/request

curl -X GET "https://api.crawlora.net/api/v1/telegram/channel?username=durov" \
  -H "x-api-key: $CRAWLORA_API_KEY"

API key authentication Error handling guide Rate limits and credits Telegram Public Channel API

How to use Telegram endpoints

Step 1
Size a channel before reading it
/telegram/channel with a public username (with or without @, or a t.me link) returns title, description, verification badge, subscriber count and photo, video, file and link counters. For @telegram on 2026-10-27, subscribers_approximate was false, so 9,239,233 is an exact figure, and files_count was 0 while videos_count was 228. Check that flag before comparing channels.
Step 2
Page backwards with next_before
/telegram/channel-posts returns 20 posts per page, newest first. The first page ran from post 460 down to 441 and returned next_before 441 with has_more true; pass it as before for the next older page. A query term searches inside the channel, and a search with no matches returns an empty list, not an error.
Step 3
Group posts into bursts before counting them
Those 20 posts fall on four days: 6 posts on 2026-08-26 (ids 455 to 460, published within about 90 seconds), 5 on 2026-07-19, 4 on 2026-06-18 and 5 on 2026-05-14. Each is a feature drop, with a summary post linking the blog. Count by publish day, not by post, if you want a cadence, and note that the newest post on 2026-10-27 was still the one from 2026-08-26.
Step 4
Treat views as rounded and links as noisy
Views came back as round numbers such as 2,120,000 and 1,040,000, so differences below roughly ten thousand are not meaningful. The links array on a post also lists sibling posts in the same burst (t.me/telegram/455 to 460), so drop links that point back to the channel when you want outbound references. A post can be marked edited, as post 455 was.
Step 5
Look up one post by id
Pass the username and a post id from the listing to /telegram/post. Keep the returned source identity and retrieval time with the record, because views and reactions keep changing.
Step 6
Use the group route only for groups
/telegram/group resolves public groups. The channel route does not support private channels, groups, bots or user accounts, and returns an error naming which kind of name you passed, which is a cheap way to classify an unknown username.