> Documentation index: https://docs.scrapier.io/llms.txt
> Auth: header `X-API-Key: <key>` · Base: https://api.scrapier.io/api/v2 · Synchronous; paginate with `cursor` ← `data.next_cursor`.

# Telegram Single Post

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

`GET|POST https://api.scrapier.io/api/v2/telegram-single-post/` · 1 credit per successful call · Single lookup

## 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

```bash
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
```

```python
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"])
```

POST with a JSON body works too (same parameters; the body is merged over the query string).

## Parameters

| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| `X-API-Key` (header) | string | yes | — | Your API key. |
| `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. |
| `use_proxy` | boolean | no | `true` | Route the request through Scrapier's residential proxy pool. Default: `true`. Leave as is unless support tells you otherwise. |
| `raw_data` | boolean | no | `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

HTTP 200. Results are in `data.post`. Sample from the live catalog, arrays trimmed to 3 items.

```json
{
  "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
  }
}
```

## 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

Single lookup: everything comes back in one call and `next_cursor` is always `null`.

## Errors

Failed calls are free. Branch on HTTP status; the message is in `error` (or `detail`). See https://docs.scrapier.io/errors.md

- **400** Bad input. The exact message varies by endpoint. `{"success":false,"error":"…"}`
- **402** Balance below the endpoint's price. `{"error":"Insufficient credits. Buy more to scrape more.","balance":1,"required":2}`
- **403** Invalid or unknown API key. `{"detail":"Authentication service unavailable or invalid API key."}`
- **429** Throttled — wait for Retry-After. `{"detail":"Request was throttled. Expected available in N seconds."}`
- **404** unknown slug · **503** busy (retry after `Retry-After`) · **5xx** upstream failure or timeout (retry with backoff).

## Notes

- 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.

## Related

- [Telegram Channel Profile + Messages](https://docs.scrapier.io/api-reference/telegram/telegram-channel.md): Structured Telegram data: send `urls`. Cursor-paginated, 1 credit per successful call.
