Telegram Single Post
Structured Telegram data: send urls. Single lookup, 1 credit per successful call.
GET · POST1 credit / successful callSingle lookup
Overview
Section titled “Overview”Call GET /api/v2/telegram-single-post/ with urls. The results are in data.post. 1 optional parameter refines the call (see Parameters).
Request
Section titled “Request”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 210const params = new URLSearchParams({ urls: "https://t.me/durov/543" });
const res = await fetch(`https://api.scrapier.io/api/v2/telegram-single-post/?${params}`, { headers: { "X-API-Key": "YOUR_API_KEY" }, signal: AbortSignal.timeout(210_000),});const body = await res.json();if (!res.ok) throw new Error(body.error ?? body.detail ?? `HTTP ${res.status}`);
console.log(body.data.post);import requests
resp = requests.get( "https://api.scrapier.io/api/v2/telegram-single-post/", headers={"X-API-Key": "YOUR_API_KEY"}, params={"urls": "https://t.me/durov/543"}, timeout=210,)body = resp.json()if not resp.ok: raise RuntimeError(body.get("error") or body.get("detail"))
print(body["data"]["post"])curl -X POST "https://api.scrapier.io/api/v2/telegram-single-post/" \ -H "X-API-Key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"urls":"https://t.me/durov/543"}' \ --max-time 210Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
X-API-Key header | string | yes | — | Your API key from the dashboard. |
urls | string | yes | e.g. https://t.me/durov/543 | Public t.me post URL. Lookup endpoint -- next_cursor null. |
cursor | string | no | — | 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
| Name | Type | Default | Description |
|---|---|---|---|
use_proxy | boolean | true | Route the request through Scrapier's residential proxy pool. Default: true. Leave as is unless support tells you otherwise. |
raw_data | boolean | false | When 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. |
Response
Section titled “Response”{ "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 }}Bad input. The exact message varies by endpoint.
{ "success": false, "error": "…"}Balance below the endpoint’s price.
{ "error": "Insufficient credits. Buy more to scrape more.", "balance": 1, "required": 2}Invalid or unknown API key.
{ "detail": "Authentication service unavailable or invalid API key."}Throttled — wait for Retry-After.
{ "detail": "Request was throttled. Expected available in N seconds."}Sample from the live catalog; arrays trimmed to 3 items. Results are in data.post.
Response fields
Section titled “Response fields”| Field | Type | Example | Description |
|---|---|---|---|
urls | string | https://t.me/durov/543 | — |
post | object | {…} | The results. |
next_cursor | null | null | Pass back as cursor for the next page. null on the last page. |
post.input_url | string | https://t.me/durov/543 | — |
post.success | boolean | true | — |
post.id | string | 543 | — |
post.channel_handle | string | durov | — |
post.url | string | https://t.me/durov/543 | — |
post.author_name | string | Pavel Durov | — |
post.author_url | string | https://t.me/durov | — |
post.text | string | Telegram has applied for the .gram domain zon… | — |
post.published_at | string | 2026-08-18T17:37:31+00:00 | — |
post.view_count | integer | 3600000 | — |
post.view_count_text | string | 3.6M | — |
post.reactions | array | [1 item] | — |
post.reaction_count | integer | 111800 | — |
post.forwarded_from | null | null | — |
post.media | array | [] | — |
post.link_preview | null | null | — |
post.scraped_at | string | 2026-09-24T13:45:36.376Z | — |
Pagination
Section titled “Pagination”Returns everything in one call; next_cursor is always null.
Errors
Section titled “Errors”Failed calls are free. Branch on the HTTP status and read the message from error (or detail). Full details in Errors.
| Status | Meaning | Retry? | Charged? |
|---|---|---|---|
400 | Bad or missing input. | No — fix the params | No |
401 / 403 | Missing, invalid or revoked API key. | No — fix the key | No |
402 | Out of credits (body has balance). | No — top up | No |
404 | Unknown endpoint slug. | No — check the slug | No |
429 / 503 | Busy or throttled. | Yes — after Retry-After | No |
5xx | Target site or upstream failure, or timeout. | Yes — with backoff | No |
- The response data carries its own
successfield from the scraper. The outersuccessis what counts: an HTTP 200 with outersuccess: trueis billed, even if the inner field says otherwise.
Related
Section titled “Related”- Telegram Channel Profile + Messages — Structured Telegram data: send
urls. Cursor-paginated, 1 credit per successful call.