> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). The sections below mirror the orientation block in [`/llms.txt`](https://www.socialfetch.dev/llms.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need a structured operation inventory. The catalog covers documented operations with on-site reference pages.

## This page

- **On-site (HTML):** [https://www.socialfetch.dev/docs/api/v1/telegram/channels/handle/posts/get](https://www.socialfetch.dev/docs/api/v1/telegram/channels/handle/posts/get)
- **Markdown (.mdx) URL:** [https://www.socialfetch.dev/docs/api/v1/telegram/channels/handle/posts/get.mdx](https://www.socialfetch.dev/docs/api/v1/telegram/channels/handle/posts/get.mdx)

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** [https://www.socialfetch.dev/openapi.json](https://www.socialfetch.dev/openapi.json)

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [SDK reference](https://www.socialfetch.dev/docs/sdk-reference.mdx) — exhaustive SDK method inventory and route mapping for agents, tooling, and power users.
- [Choose the right endpoint](https://www.socialfetch.dev/docs/choose-endpoint.mdx) — task-oriented route selection for smoke tests, profiles, list endpoints, and single-item lookups.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — fast comparison of identifiers, pagination, outcomes, media download, and SDK coverage.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).

---
# List Telegram channel posts (https://www.socialfetch.dev/docs/api/v1/telegram/channels/handle/posts/get)

## Summary

List recent posts from a public Telegram channel. Groups are not supported.

**Tags:** `Telegram`

## HTTP

- **Method:** GET
- **Path:** `/v1/telegram/channels/{handle}/posts`
- **Base URL:** `https://api.socialfetch.dev`

## Capability summary

- **SDK mapping:** `client.telegram.getChannelPosts({ handle: "durov", cursor? })`
- **Accepted identifiers:** `handle` (path)
- **Pagination:** cursor via `cursor`
- **Business outcome field:** `data.lookupStatus` with values `found`, `not_found`, `restricted`

## Credits

- **Base:** 1 credit per successful lookup.
- **Maximum on success (200):** 1 credit.
- **Normalization failure (502):** 1 credit charged.
- **Authoritative field:** `meta.creditsCharged`.

## Authentication

- **`x-api-key`**: API key (`sfk_...`)

## Parameters

### `handle` (path)

- **Required:** yes
- **Constraints:** type `string`; minLength: 1; maxLength: 200
- **Description:** Telegram public username (channel or group), with or without leading @.

### `cursor` (query)

- **Required:** no
- **Constraints:** type `string`
- **Description:** Opaque pagination cursor from a previous response. Omit for the first page.

## Pagination

This endpoint supports cursor-based pagination via the `cursor` query parameter:

- Read the next cursor from the successful response JSON (see the response schema for the exact field path).
- Omit `cursor` on the first request.
- Repeat until there is no next cursor or the API indicates there are no more results.

## Responses (status codes)

- **200**: Lookup result. Check `data.lookupStatus` for `found`, `not_found`, or `restricted` before reading `data.posts`. When `found`, use `data.nextCursor` for pagination when `data.hasMore` is true.
- **400**: Invalid handle or pagination cursor
- **401**: Missing or invalid API key
- **402**: Insufficient credits
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed from the upstream response.
- **503**: Service temporarily unavailable; safe to retry with backoff.

## Response body (200)

Lookup result. Check `data.lookupStatus` for `found`, `not_found`, or `restricted` before reading `data.posts`. When `found`, use `data.nextCursor` for pagination when `data.hasMore` is true.

### Field outline

- **data** (required) — type `object`. Endpoint-specific response payload.
  - **lookupStatus** (required) — type `string`; enum: found, not_found, restricted. Domain outcome of the channel lookup. Always check this before reading `posts`.
  - **posts** (required) — type `array`. Posts in reverse chronological order (newest first) when lookupStatus is `found`. Empty when `not_found` or `restricted`.
    - _items:_
      - **postId** (required) — type `string`. Unique post ID within the channel.
      - **text** (required) — type `string`; nullable. Post text as simplified HTML (<br> line breaks, <a href> links, custom tg-emoji expanded to unicode, common HTML entities decoded so arrows and quotes read naturally in JSON). Null if the post contains only media.
      - **date** (required) — type `string`; nullable. ISO 8601 publication timestamp.
      - **views** (required) — type `integer`; nullable. View count from the public feed. Telegram may abbreviate large values (e.g. 1.13M → 1130000). Null for very recent posts.
      - **forwardedFrom** (required) — type `string`; nullable. Original channel name if this post was forwarded.
      - **replyTo** (optional) — type `object`; default: `null`; nullable. Reply/quote preview when this post replies to another channel message; null otherwise.
        - **postId** (required) — type `string`. Numeric post ID of the message being replied to, from the public t.me link in the reply preview.
        - **authorName** (required) — type `string`; nullable. Channel or author name shown in the reply preview bar.
        - **text** (required) — type `string`; nullable. Preview snippet of the replied-to message as shown in the embed (often truncated). May be a short media label such as Photo when Telegram does not show body text.
      - **photoUrls** (required) — type `array`. Photo URLs from Telegram CDN. May expire over time; download promptly if needed.
        - _items:_
          - type `string`
      - **videoUrl** (required) — type `string`; nullable. Video URL if the post contains a video. May expire over time; download promptly if needed.
      - **reactions** (optional) — type `array`; default: ``. Reaction counts shown on the public preview page. Empty when Telegram omits them for a post.
        - _items:_
          - **emoji** (required) — type `string`; nullable. Unicode reaction emoji when Telegram exposes it in the public HTML (including Stars as ⭐). Null for premium/custom animated reactions — use customEmojiId and emojiImageUrl.
          - **customEmojiId** (optional) — type `string`; default: `null`; nullable. Telegram custom emoji document id when the reaction uses a premium/custom emoji.
          - **emojiImageUrl** (optional) — type `string`; default: `null`; nullable. Preview image URL for custom emoji reactions (from Telegram's public emoji metadata). Null for standard unicode reactions.
          - **isPaid** (optional) — type `boolean`; default: `false`. True when the reaction is a Telegram Stars paid reaction.
          - **count** (required) — type `integer`; minimum: 0. Number of users who added this reaction.
  - **nextCursor** (required) — type `string`; nullable. Pagination cursor for the next page. Null if no more posts.
  - **hasMore** (required) — type `boolean`. Whether older posts are available. True when Telegram's public feed HTML includes a load-more control for earlier messages.
- **meta** (required) — type `object`. Metadata describing the request and billing outcome.
  - **requestId** (required) — type `string`; minLength: 1. Unique request identifier for tracing this API call.
  - **creditsCharged** (required) — type `integer`; minimum: 0. Credits charged for this request.
  - **version** (required) — type `string`; enum: v1. Public API version that served the response.

### Example JSON (found)

```json
{
  "data": {
    "lookupStatus": "found",
    "posts": [
      {
        "postId": "100",
        "text": "Hello world",
        "date": "2026-01-15T10:00:00+00:00",
        "views": 1200,
        "forwardedFrom": null,
        "replyTo": null,
        "photoUrls": [],
        "videoUrl": null,
        "reactions": []
      }
    ],
    "nextCursor": null,
    "hasMore": false
  },
  "meta": {
    "requestId": "req_01example",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Example JSON (not_found)

```json
{
  "data": {
    "lookupStatus": "not_found",
    "posts": [],
    "nextCursor": null,
    "hasMore": false
  },
  "meta": {
    "requestId": "req_01example_posts_nf",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Example JSON (restricted)

```json
{
  "data": {
    "lookupStatus": "restricted",
    "posts": [],
    "nextCursor": null,
    "hasMore": false
  },
  "meta": {
    "requestId": "req_01example_posts_restricted",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Machine-readable error codes

When an error JSON body is returned, it may include one of these `error.code` values (derived from the OpenAPI schemas for this operation; additional codes may exist at runtime):

- `bad_request`

## Error handling & retries

Interpret HTTP status codes using the descriptions below. Do not assume a JSON body unless the OpenAPI schema defines one for that status.

- **400**: Invalid handle or pagination cursor **Retry:** Fix the request; retrying the same invalid payload will not help.
- **401**: Missing or invalid API key **Retry:** Fix the API key first; retrying without changes will not help.
- **402**: Insufficient credits **Retry:** Do not retry without resolving billing/credits (retrying the same request will not help).
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed from the upstream response. **Retry:** May be transient; a few retries with backoff are reasonable.
- **503**: Service temporarily unavailable; safe to retry with backoff. **Retry:** Usually safe to retry with exponential backoff and jitter.

### Suggested client defaults

- Send the API key using the `x-api-key` header on every request.
- On `503` (and sometimes `502`), retry with backoff; cap retries and surface a clear error to the user.
- On `402`, surface an actionable billing message rather than blind retries.

## Examples

### TypeScript SDK

```typescript
import { SocialFetchClient } from "@socialfetch/sdk";

const client = new SocialFetchClient({
  apiKey: process.env.SOCIALFETCH_API_KEY!,
});

const result = await client.telegram.getChannelPosts({
  handle: "durov",
});

if (!result.ok) {
  console.error(result.error);
} else {
  console.log(result.value.data);
}
```

### Node.js

```javascript
const response = await fetch(
  "https://api.socialfetch.dev/v1/telegram/channels/durov/posts",
  {
    headers: {
      "x-api-key": "YOUR_API_KEY",
    }
  }
);

const data = await response.json();
console.log(data);
```

### cURL

```bash
curl "https://api.socialfetch.dev/v1/telegram/channels/durov/posts" \
  -H "x-api-key: YOUR_API_KEY"
```

### Python

```python
import requests

response = requests.get(
    "https://api.socialfetch.dev/v1/telegram/channels/durov/posts",
    headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()
print(data)
```

### Example: next page (pagination)

After a successful response, if pagination is not finished, request the next page using `cursor` (URL-encode when composing the query string):

```javascript
const previous = await response.json();
const nextCursor = previous?.data?.page?.nextCursor;
const hasMore = previous?.data?.page?.hasMore;
if (!hasMore || nextCursor == null) {
  // no more pages
} else {
  const nextUrl = new URL("https://api.socialfetch.dev/v1/telegram/channels/charlidamelio/posts");
  nextUrl.searchParams.set("cursor", nextCursor);
  // optionally preserve sort: nextUrl.searchParams.set("sortBy", "latest");
  const nextResponse = await fetch(nextUrl.toString(), {
    headers: { "x-api-key": "YOUR_API_KEY" },
  });
  const nextData = await nextResponse.json();
}
```