← 瀏覽全部 API
Telegram post API
一次 REST 呼叫取得 Telegram post 資料——以 FetchPI 全平台共用的穩定 JSON 結構標準化輸出。
- 1 個已發布端點
- GET /v1/telegram/channels/{username}/posts/{id}
契約摘要(英文): Get a normalized Telegram channel message (capability telegram.post)
- 標準化回應實體
- telegram/post
- capability
- telegram.post
每個回應都附帶新鮮度(cache / default / live)與計費中繼資料。
使用場景
- 為內容分析管線提供結構化的 {{platform}} 貼文:內文、指標、時間戳記與媒體引用。
- 支撐需要原始內容與互動數據的審核、研究與監測流程。
- 以穩定的標準化 JSON 歸檔 {{platform}} 內容,告別脆弱的網頁爬取。
回應欄位
Telegram Post (normalized)
Normalized Telegram post — the ONLY upper-layer format; provider-private fields are dropped. Serves telegram.post and the post lists of /v1/telegram.
| 欄位 | 類型 | 必填 | 說明 |
|---|---|---|---|
| id | string | 必填 | Platform-native post id (pk / activity id / message id / cell id). |
| platform | "telegram" | 必填 | — |
| type | "post" | 必填 | — |
| author.id | string | 必填 | Author platform id. |
| author.username | string | 必填 | Author addressing key without leading @. |
| author.display_name | string | null | 必填 | Author display name. |
| author.verified | boolean | 必填 | — |
| text | string | null | 必填 | Post text (null for media-only posts). |
| created_at | string | 必填 | Post publish time, UTC RFC3339. |
| metrics.likes | integer | 必填 | Reaction count; always emitted, 0 when the vendor hides it (channels carry no like surface). |
| metrics.comments | integer | 必填 | Discussion-group comment count. |
| metrics.shares | integer | 必填 | Forward count. |
| metrics.views | integer | 必填 | Message view count. |
| attachments | object[] | 可選 | Media attachments (max 8): photo urls and/or the video block. |
| fetched_at | string | 必填 | Normalization time of the stored snapshot (UTC). |
欄位備註為契約英文原文。
回應中繼資料
| 欄位 | 類型 | 必填 | 說明 |
|---|---|---|---|
| mode | cache | default | live | 必填 | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | 可選 | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | 必填 | Which layer served the response (PRD §10). |
| stale | boolean | 可選 | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | 必填 | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | 必填 | — |
欄位備註為契約英文原文。
請求與回應範例
GET
/v1/telegram/channels/{username}/posts/{id}curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/telegram/channels/newdev/posts/1842951234567890123"{
"data": {
"id": "8359000000001002",
"platform": "telegram",
"type": "post",
"author": {
"id": "8355000122",
"username": "meshdata_tg",
"display_name": "MeshData 频道",
"verified": false
},
"text": "频道消息:数据 API 发布。",
"created_at": "2026-09-16T11:20:00Z",
"metrics": {
"likes": 0,
"comments": 2,
"shares": 120,
"views": 51000
},
"fetched_at": "2026-09-21T09:00:00Z"
},
"meta": {
"request_id": "req_01HTXQ8Z9HTQ",
"freshness": {
"mode": "default",
"age_seconds": 0,
"source_layer": "upstream",
"stale": false
},
"billing": {
"amount_credits": 100,
"cache_hit": false
}
}
}免費試用
註冊免費帳號、取得 API Key,即可在瀏覽器版 Playground 直接呼叫該端點。
在 Playground 試用該端點的參數表、錯誤碼與回應語義見 API 文件。
查看端點參考常見問題
回應包含哪些內容欄位?
回應攜帶標準化的內容實體(內文、作者、時間戳記、互動指標與媒體引用),欄位見下方欄位表,並附帶新鮮度與計費中繼資料。
可以免費試用該端點嗎?
可以——註冊帳號、取得 API Key 後,即可在主控台的 Playground 呼叫該端點。
post 能力怎麼計費?
Data API 按請求以點數計費,cache/live 新鮮度有不同倍率。目前各能力的價格以價格頁為準。