Telegram Search API
Scrape Telegram Search data with one API call. Finds public Telegram channels by keyword, so you can pick the channels to read with `/v1/telegram/profile` and `/v1/telegram/profile/posts`. Channels are discovered through a public web search index limited to t.me pages, so this finds what that index has already seen: it is not real time, a channel or message from the last few days may not appear yet, and private channels and invite-only groups never appear. Returns one row per channel, in the order the search found them, on the same Author shape `/v1/telegram/profile` returns: `author.username` is the public handle (pass it as `handle`), `author.url` is `https://t.me/<handle>`, and `author.display_name` is the channel's title when the search result carried it (null when the result showed only the handle). `author.ext.search_hit` says how the channel was found: `match` is `channel_page` (the channel's own page) or `post_in_channel` (a message or the message preview), `title` and `snippet` are the hit as the index showed it, `evidence_url` is the first page that matched, and `matched_urls` lists every t.me page the search matched for that channel, so you can open the exact messages. The snippet is the index's text, not the channel's description, so `author.bio` stays null on a plain call, as do `author.followers`, `author.avatar_url` and `author.verified`. Send `include=details` and every channel is joined, in the same call, to the profile lookup: the exact subscriber count (`author.followers`), the description (`author.bio`), the avatar, the verified flag and, where it was null, the title land on each row. Words in `query` match loosely; put a phrase in double quotes to require it, and add `-word` to exclude a word. Cost: 2 credits for the page, plus 1 credit per channel filled from a fresh lookup with `include=details` (at most 10 a page, so 12 credits at most); channels already in cache are free, channels that could not be filled are refunded, and a search that finds no public channel is a 404 at 0 credits. Time: a plain page takes about 2 to 12 seconds; `include=details` adds a few seconds on a fresh page (the lookups run in parallel and the call waits for the slowest, never more than 10 seconds) and nothing when the channels are already cached. The response carries a `hydration` block itemising rows, lookups, cache hits, credits and milliseconds. A page holds up to 10 channels, fewer when several hits belong to one channel. Forward `pagination.next_cursor` as `cursor` for the next page; the same channel can appear again on a later page.
Last updated October 2026Maintained by the SocialCrawl team
Returns the public Telegram channels a web search index has seen for your keywords, one row per channel, with the pages that matched and, on request, exact subscriber counts.
Use it to find channels selling or discussing a product or brand, then read them with profile/posts. The index lags behind Telegram, so treat it as discovery, not a live feed.
Searching 68 platforms in parallel
What can you do with the Search API?
The Search endpoint gives you structured Telegram data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/telegram/search?query=byd+spare+parts&date_posted=last-hour"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/telegram/search",
params={
'query': 'byd spare parts',
'date_posted': 'last-hour',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/telegram/search?query=byd+spare+parts&date_posted=last-hour",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();Parameters worth sending
date_posted=last-hourOnly posts from this time window.
Parameters
| Parameter | Required | Description |
|---|---|---|
| query | Yes | Keywords describing the channels or messages to find, for example `byd spare parts`. Put a phrase in double quotes to require it. Keywords only: the search is already limited to public Telegram pages, so a `site:` operator is refused before billing. |
| page | No | Page number, starting at 1. Forwarding `pagination.next_cursor` as `cursor` does the same. |
| date_posted | No | Only pages the search index dates within this window: last-hour, last-day, last-week, last-month or last-year. Useful for monitoring new activity. (last-hour | last-day | last-week | last-month | last-year) |
| region | No | Two-letter country code (US, AE, IN, KR) whose results to prefer. |
| limit | No | Return at most this many channels from the page (1 to 10). With `include=details` it also lowers the credits held, one per channel. |
| include | No | Set to `details` (one token only) to fill, on every channel in this one call, `author.followers` (the exact subscriber count), `author.bio` (the description), `author.avatar_url`, `author.verified`, and the title where it was null. Holds 1 credit per channel (at most 10 a page) and keeps only the channels filled from a fresh lookup; channels already in cache and channels the lookup cannot fill are refunded, so a page is never more than 12 credits. Read `data.hydration` for the rows, the credits held and kept, and the time. Without it the call is unchanged. (details) |
What does the Telegram Search API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "tiktok",
"endpoint": "/v1/tiktok/search/users",
"data": {
"items": [
{
"author": {
"id": "user_0e9522",
"username": "user_759369",
"display_name": "user_f0b019",
"avatar_url": "https://example.com/avatars/user_0ab01c.png",
"bio": null,
"verified": null,
"followers": 4214875,
"following": 1,
"posts_count": 2341,
"likes_count": 62731828,
"url": null,
"location": null
}
},
{
"author": {
"id": "user_d26411",
"username": "user_1f51ed",
"display_name": "user_1f51ed",
"avatar_url": "https://example.com/avatars/user_a81e65.png",
"bio": null,
"verified": null,
"followers": 1780390,
"following": 1,
"posts_count": 995,
"likes_count": 10060260,
"url": null,
"location": null
}
},
{
"author": {
"id": "user_679d13",
"username": "user_c5d687",
"display_name": "user_8803ea",
"avatar_url": "https://example.com/avatars/user_67de4c.png",
"bio": null,
"verified": null,
"followers": 338243,
"following": 374,
"posts_count": 464,
"likes_count": 2140124,
"url": null,
"location": null
}
}
],
"next_cursor": "30",
"total": 30,
"dropped": 0
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req-8Kq2ZmR4vT9xLb3P",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMzAiLCJwIjoiY3Vyc29yIn0",
"has_more": true,
"page_size": 30
},
"redacted": true
}Example captured from the TikTok API. Every SocialCrawl endpoint returns this same unified schema, so your Telegram Search response has the same fields.
How does the Telegram Search API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 68 platforms covering 10B+ monthly active users.
One schema, every platform
Query 68 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Ready to scrape Telegram Search data?
Get your API key and start pulling Telegram data in under 60 seconds.
