Skip to content

Structured Telegram data: send urls. Single lookup, 1 credit per successful call.

GET · POST1 credit / successful callSingle lookup
GEThttps://api.scrapier.io/api/v2/telegram-single-post/Open in Playground

Call GET /api/v2/telegram-single-post/ with urls. The results are in data.post. 1 optional parameter refines the call (see Parameters).

Terminal window
curl -G "https://api.scrapier.io/api/v2/telegram-single-post/" \
-H "X-API-Key: YOUR_API_KEY" \
--data-urlencode "urls=https://t.me/durov/543" \
--max-time 210
NameTypeRequiredDefaultDescription
X-API-Key headerstringyes—Your API key from the dashboard.
urlsstringyese.g. https://t.me/durov/543Public t.me post URL. Lookup endpoint -- next_cursor null.
cursorstringno—Pagination cursor returned in the previous response's next_cursor. Pass it back unchanged to fetch the next page. When next_cursor is null, you have reached the last page.
Advanced
NameTypeDefaultDescription
use_proxybooleantrueRoute the request through Scrapier's residential proxy pool. Default: true. Leave as is unless support tells you otherwise.
raw_databooleanfalseWhen true, the response carries the full raw upstream payload(s) the scraper received (GraphQL / JSON API bodies, HTML, embedded JSON-LD -- exactly as the platform returned them) under raw_responses, in place of the formatted items. When false (default) you get the formatted output. Pagination (cursor / next_cursor) works the same in both modes.
{
"success": true,
"data": {
"urls": "https://t.me/durov/543",
"post": {
"input_url": "https://t.me/durov/543",
"success": true,
"id": "543",
"channel_handle": "durov",
"url": "https://t.me/durov/543",
"author_name": "Pavel Durov",
"author_url": "https://t.me/durov",
"text": "Telegram has applied for the .gram domain zone...",
"published_at": "2026-08-18T17:37:31+00:00",
"view_count": 3600000,
"view_count_text": "3.6M",
"reactions": [
{
"emoji": "⭐",
"emoji_id": null,
"count": 17300,
"count_text": "17.3K"
}
],
"reaction_count": 111800,
"forwarded_from": null,
"media": [],
"link_preview": null,
"scraped_at": "2026-09-24T13:45:36.376Z"
},
"next_cursor": null
}
}

Sample from the live catalog; arrays trimmed to 3 items. Results are in data.post.

FieldTypeExampleDescription
urlsstringhttps://t.me/durov/543—
postobject{…}The results.
next_cursornullnullPass back as cursor for the next page. null on the last page.
post.input_urlstringhttps://t.me/durov/543—
post.successbooleantrue—
post.idstring543—
post.channel_handlestringdurov—
post.urlstringhttps://t.me/durov/543—
post.author_namestringPavel Durov—
post.author_urlstringhttps://t.me/durov—
post.textstringTelegram has applied for the .gram domain zon…—
post.published_atstring2026-08-18T17:37:31+00:00—
post.view_countinteger3600000—
post.view_count_textstring3.6M—
post.reactionsarray[1 item]—
post.reaction_countinteger111800—
post.forwarded_fromnullnull—
post.mediaarray[]—
post.link_previewnullnull—
post.scraped_atstring2026-09-24T13:45:36.376Z—

Returns everything in one call; next_cursor is always null.

Failed calls are free. Branch on the HTTP status and read the message from error (or detail). Full details in Errors.

StatusMeaningRetry?Charged?
400Bad or missing input.No — fix the paramsNo
401 / 403Missing, invalid or revoked API key.No — fix the keyNo
402Out of credits (body has balance).No — top upNo
404Unknown endpoint slug.No — check the slugNo
429 / 503Busy or throttled.Yes — after Retry-AfterNo
5xxTarget site or upstream failure, or timeout.Yes — with backoffNo
  • The response data carries its own success field from the scraper. The outer success is what counts: an HTTP 200 with outer success: true is billed, even if the inner field says otherwise.