Telegram Profile Posts API
Returns one page of a channel's public posts, newest first, each with its text, publish time, view count, per-emoji reaction breakdown, and direct photo or video URLs.
GET /v1/telegram/profile/postsLast updated November 2026Maintained by the SocialCrawl team
When to use the Telegram Profile Posts API
Use it to read or archive a channel's history. Page size varies, so keep passing the cursor until it comes back empty rather than stopping on a short page.
From the API reference
Returns one page of recent public posts from a Telegram channel or group, newest page first. Each post carries its text, publish time, view count, the per-emoji reaction breakdown, and direct media URLs for photos and videos. Pass the returned cursor to walk further back through the channel's history. Page size varies because photo albums count as one post and service messages are skipped, so a short page does not mean the end of the channel: keep paging until the cursor is absent. Send q to search inside the channel instead: you get one page of the newest messages that contain every word of q (up to about 20), at the same price, with no cursor.
Searching 69 platforms in parallel
What can you do with the Profile Posts API?
The Profile Posts endpoint gives you structured Telegram data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
# GET /v1/telegram/profile/posts: 1 credit per page. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
# --max-time 13: this endpoint's measured p99 latency x 1.5.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
# Next page: send pagination.next_cursor back as cursor until pagination.has_more is false.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 13 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/telegram/profile/posts?handle=telegram" && cat response.json# GET /v1/telegram/profile/posts: 1 credit per page. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 13 # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/telegram/profile/posts"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"handle": "telegram",
}
# Walk the list: send pagination.next_cursor back as cursor until has_more is false.
MAX_PAGES = 10 # each page is one call
items = []
for _ in range(MAX_PAGES):
body = socialcrawl(params)
if body is None:
break
items.extend(body["data"]["items"])
page = body.get("pagination") or {}
if not page.get("has_more") or not page.get("next_cursor"):
break
params["cursor"] = page["next_cursor"]
print(f"{len(items)} items")// GET /v1/telegram/profile/posts: 1 credit per page. Cache hits are free and failed calls are refunded.
// Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 13_000; // this endpoint's measured p99 latency x 1.5.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/telegram/profile/posts");
url.searchParams.set("handle", "telegram");
// Walk the list: send pagination.next_cursor back as cursor until has_more is false.
const MAX_PAGES = 10; // each page is one call
const items: unknown[] = [];
for (let page = 0; page < MAX_PAGES; page++) {
const body = await socialcrawl(url);
if (!body) break;
items.push(...body.data.items);
const next = body.pagination?.next_cursor;
if (!body.pagination?.has_more || !next) break;
url.searchParams.set("cursor", next);
}
console.log(`${items.length} items`);Parameters
| Parameter | Required | Description |
|---|---|---|
| handle | Yes | Public Telegram handle, with or without the leading @, or a t.me channel URL |
| cursor | No | Cursor from the previous page's pagination block. Omit it for the most recent posts. |
| q | No | Words to search for inside the channel, for example `cheap watches`. Returns one page of the newest messages whose text contains every word (put a phrase in double quotes to require it as written), at the same price as a plain page. Telegram's own search also matches other forms of a word (`watch` for `watches`); those messages are left out, because they do not contain the words. A search page has no cursor, so `q` cannot be combined with `cursor`. |
| since | No | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| until | No | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| max_pages | No | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| max_items | No | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| max_credits | No | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |
What does the Telegram Profile Posts 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": "telegram",
"endpoint": "/v1/telegram/profile/posts",
"data": {
"items": [
{
"post": {
"id": "441",
"url": "https://t.me/telegram/441",
"content": {
"text": "Bot-to-Bot Communication. Bots are now able to respond to other bots, not just users. AI enthusiasts can utilize this to create custom workflows with autonomous agents. May Features 1 • 2 • 3 • 4 • 5 • More",
"media_urls": [
"https://cdn1.telesco.pe/file/c01503a63e.mp4?token=F1gyI_bSWGGmbhhTHD0hMW_MtU4-kbyesJeEJn3igVvTkXoBNkzhVz4sQNFp1jDHFmXnCCA3EZI5bGQ4QmxgfRef2vsj_SlJBV5NLH_cNSFZZ7c0qGtZ1p_HZZg9-zyq1oc42IFQJU0mqEoikbw1CkYYcKz1mEUCMDNNlS8ZAXrmGLI2Fdhxz3GL52gMgW1tK-AMpbA9x9gGTGICfMvtV-F8AVQ15qODzIBYK7CnoDgcXeYtML9zpg4XCMTj986PEfdu9YJgKkwSIX2-qhdqNZ1f3JJ1jEFOjYSjemyguBA2uLcizrhgPx_QUS_MjSt0fozZh7UCF5iHuR-Nt9-t8w"
],
"thumbnail_url": "https://cdn1.telesco.pe/file/TZVrsEkjo46ptIfD67o-2JlmqjBFjV8b0e84pGqKspohb_QAe-8eoQcPRzbfUbZauMYNqgJPm8P-S0hNaahM1u_5QEgK5k6GRVwNxfV3NihTEbNKK6r3Ge1MkFJkhyQf2HzVN9svBi39Qq2KFm41_ww4ITTv-Wd5DQqkYqTxOQb5j_YbzMlf5K7TlHBhbrnqhjKUK9XX1tac9f4LwjwC-UonFh6F27LJ718u7-PVV4O_82W4k5AEw1oUpOWW6KvrduB3pKgydwsrY9GGRUQimXMoW5QgtpfohngHQVtHXNqA2pKeMWTyKIVOcGKEPKx-0Ikb3XHmkwvVY92c9vFV7g",
"duration_seconds": 6
},
"author": {
"username": "telegram",
"display_name": "user_41eca1",
"avatar_url": null,
"verified": null
},
"engagement": {
"views": 1510000,
"likes": 0,
"comments": null,
"shares": null,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": null,
"deleted": false
},
"published_at": "2026-05-14T16:08:31.000Z",
"ext": {
"reaction_counts": []
}
},
"computed": {
"engagement_rate": 0,
"language": "en",
"content_category": "other",
"estimated_reach": 1812000
}
},
{
"post": {
"id": "442",
"url": "https://t.me/telegram/442",
"content": {
"text": "Chat Automation in Profiles. Every Telegram user can now connect a bot to their profile – and let it respond to messages on their behalf. May Features 1 • 2 • 3 • 4 • 5 • More",
"media_urls": [
"https://cdn1.telesco.pe/file/eb82a15bbc.mp4?token=TCgYjeeMZ8_BQes9nz1KGIc8voR2n6Lh7l82AVBjuiUI39RBC4sdSV8WASZbwiYUpQhjVUBUoF3Dra_cKLVBAUMQimR9bDswMpo1hJQUSmlLwOCu7RE_pWdDJ28L5PKSQbRke9dsBhFbUcc6zTuXu8CZmJrQ81pkU8mhZKkRxZxDt5-_4EbgrpvR36YLeC-yfDxiXmXhtROxOIQUUWlxCZdOtO3QJVIPfWSKwLjxZ69CBAOqfV1KcGujApFCEV2e_dMINn8SN-gWWI9pMD9rxwPB54NGq0IKn5ZeXWCFbsxxwnmUADypQih7RlUsyCg8gl6YTl4r9Q41hHB6ixHnaQ"
],
"thumbnail_url": "https://cdn1.telesco.pe/file/ParfGSJ07OpSSu3uYtVKx4IWRYq561PeQDj1O-r0WJ-YMq9DlL-ogwnI5NiMQ89DLsJeiCTtN1QdXpXoq4y6HTDU4gwcvl3J1tnQY8N8TWgX7keiIQDTbavkTUdgV_bBjkCUO0bcfEe_uCdpAp0SQ3PyaGH4xXgl0GR_L6KIhH3IjMFef6ix23BPFjCRprLpNp1JTnNak3dvMiRaRwB3lIpOEJ791Iz4secg-NgK4v8-kM88ugKLJXF2H9YNtB3oBUu3u4J1YxDTeMyw61sA_ZjqUa-TqfBzQ28aBY4k1fp6DXqnH8SZGOjTOrOwbUI9aV_l4jdE2WgUXg-QMBzCBA",
"duration_seconds": 9
},
"author": {
"username": "telegram",
"display_name": "user_41eca1",
"avatar_url": null,
"verified": null
},
"engagement": {
"views": 1320000,
"likes": 0,
"comments": null,
"shares": null,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": null,
"deleted": false
},
"published_at": "2026-05-14T16:08:52.000Z",
"ext": {
"reaction_counts": []
}
},
"computed": {
"engagement_rate": 0,
"language": "en",
"content_category": "other",
"estimated_reach": 1584000
}
}
],
"next_cursor": "441",
"total": null,
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiNDQxIiwiZSI6InRlbGVncmFtL3Byb2ZpbGUvcG9zdHMiLCJwIjoiY3Vyc29yIn0",
"has_more": true,
"page_size": 20
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T07:26:59.024Z",
"redacted": true
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Telegram Profile Posts 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 69 platforms covering 10B+ monthly active users.
One schema, every platform
Query 69 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"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usWhat is in each Telegram post row?
How does pagination work?
Why do pages come back with different numbers of posts?
Will I get duplicate posts across pages?
Can I get media files, not just links?
Ask AI about SocialCrawl
Ready to scrape Telegram Profile Posts data?
Get your API key and start pulling Telegram data in under 60 seconds.
