Threads-Web-API

获取帖子详情 V2(支持链接)/Get post detail V2(supports URL)

Changed on

[中文]

用途:

  • 获取Threads帖子详情(支持短代码和完整URL)
  • 价格:0.002$ / 次

参数:

返回:

  • 按角色分组的帖子数据:
    • post: 被请求的帖子本体(单个对象),含 post_id / code / caption / user / like_count / direct_reply_count / repost_count / quote_count / image_versions2 / video_versions / carousel_media 等
    • replies: 该帖的评论列表。注意这是首屏的一小部分,不是全量评论; 完整评论请调用 /fetch_post_comments
    • parent_thread: 父帖链。仅当被请求的帖子本身是一条回复时才非空
    • author_thread: 楼主自己接的串(同一作者连续发布的后续帖子)
    • pinned_replies: 置顶评论
  • 说明:角色由所在分组决定。请勿用帖子自身的 is_reply 字段判断角色—— 当被请求的帖子本身是一条回复时,它的 is_reply 也是 true
  • replies / parent_thread / author_thread / pinned_replies 恒为数组,无数据时为空数组

[English]

Purpose:

  • Get Threads post detail (supports short code and full URL)
  • Price: 0.002$ / time

Parameters:

Return:

  • Post data grouped by role:
    • post: The requested post itself (a single object), including post_id / code / caption / user / like_count / direct_reply_count / repost_count / quote_count / image_versions2 / video_versions / carousel_media, etc.
    • replies: Comments on the post. Note this is only a small first-screen subset, not the full comment list; call /fetch_post_comments for complete comments
    • parent_thread: Parent post chain. Non-empty only when the requested post is itself a reply
    • author_thread: The author's own thread continuation (subsequent posts by the same author)
    • pinned_replies: Pinned comments
  • Note: The role is determined by which group a post appears in. Do NOT use a post's own is_reply field to infer its role — when the requested post is itself a reply, its is_reply is also true
  • replies / parent_thread / author_thread / pinned_replies are always arrays, empty when there is no data

[示例/Example]

post_id = "DPVUglOjOUu"

or

url = "https://www.threads.com/@taylorswift/post/DPVUglOjOUu"

get/api/v1/threads/web/fetch_post_detail_v2

Request

  • Base URL
    https://api.tikhub.io (the document declares no server; this is the origin it was published from)
  • Auth
    HTTP bearer

Query parameters

post_idstring

帖子短代码/Post short code

urlstring

完整帖子URL/Full post URL

Response

Successful Response

codeinteger

HTTP status code | HTTP状态码

request_idstring nullable

Unique request identifier | 唯一请求标识符

messagestring

Response message (EN-US) | 响应消息 (English)

message_zhstring

Response message (ZH-CN) | 响应消息 (中文)

supportstring

Support message | 支持消息

timestring

The time the response was generated | 生成响应的时间

time_stampinteger

The timestamp the response was generated | 生成响应的时间戳

time_zonestring

The timezone of the response time | 响应时间的时区

docsstring nullable

Link to the API Swagger documentation for this endpoint | 此端点的 API Swagger 文档链接

cache_messagestring nullable

Cache message (EN-US) | 缓存消息 (English)

cache_message_zhstring nullable

Cache message (ZH-CN) | 缓存消息 (中文)

cache_urlstring nullable

The URL to access the cached result | 访问缓存结果的 URL

routerstring

The endpoint that generated this response | 生成此响应的端点

paramsunknown
dataunknown

Changes

    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      the response's property default value changed from This request will be cached. You can access the cached result directly using the URL below valid for 24 hours. Accessing the cache will not incur additional charges. to This response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again. for the status

    • info

      the response's property default value changed from 本次请求将被缓存,你可以使用下面的 URL 直接访问缓存结果,有效期为 24 小时,访问缓存不会产生额外费用。 to 本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。 for the status