Reddit-APP-API

获取Reddit APP评论回复(二级评论)/Fetch Reddit APP Comment Replies (Sub-comments)

Changed on

[中文]

用途:

  • 获取Reddit APP指定评论下的回复(二级评论/子评论)
  • 当评论节点有 more.cursor 字段时,使用此接口获取该评论的子评论

参数:

  • post_id: 帖子ID,格式如 "t3_XXXXXX"
  • cursor: 评论游标,从评论数据的 more.cursor 字段获取,格式如 "commenttree:ex:(xxx)"
  • sort_type: 排序方式,支持CONFIDENCE, NEW, TOP, HOT, CONTROVERSIAL, OLD, RANDOM

返回:

  • 指定评论下的回复JSON数据,包含:
    • 子评论列表
    • 每个子评论的详细信息(内容、作者、点赞数等)
    • 分页信息

使用步骤:

  1. 先调用 fetch_post_comments 获取帖子的一级评论
  2. 在返回数据中找到有子评论的节点(childCount > 0)
  3. 获取该节点的 more.cursor 值
  4. 使用该 cursor 调用本接口获取子评论

注意:

  • cursor 值来自评论数据的 more.cursor 字段
  • 路径示例: $.data.postInfoById.commentForest.trees[*].more.cursor
  • cursor 格式类似: "commenttree:ex:(RjiJd"

[English]

Purpose:

  • Fetch replies (sub-comments/second-level comments) under a specified Reddit APP comment
  • Use this endpoint when a comment node has more.cursor field to get its sub-comments

Parameters:

  • post_id: Post ID, format like "t3_XXXXXX"
  • cursor: Comment cursor from the more.cursor field in comment data, format like "commenttree:ex:(xxx)"
  • sort_type: Sort method, supports CONFIDENCE, NEW, TOP, HOT, CONTROVERSIAL, OLD, RANDOM

Returns:

  • JSON data of replies under the specified comment, containing:
    • List of sub-comments
    • Detailed information for each sub-comment (content, author, upvotes, etc.)
    • Pagination information

Usage Steps:

  1. First call fetch_post_comments to get top-level comments
  2. Find comment nodes with sub-comments (childCount > 0)
  3. Get the more.cursor value from that node
  4. Use that cursor to call this endpoint to fetch sub-comments

Note:

  • cursor value comes from the more.cursor field in comment data
  • Path example: $.data.postInfoById.commentForest.trees[*].more.cursor
  • cursor format example: "commenttree:ex:(RjiJd"

[示例/Example]

post_id="t3_1qmup73" cursor="commenttree:ex:(RjiJd" sort_type="CONFIDENCE" need_format=false

get/api/v1/reddit/app/fetch_comment_replies

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

languagestring

返回内容使用的语言,采用 IETF 语言标签;默认 en-US / Preferred response language as an IETF language tag; default: en-US

post_idstring required

帖子ID/Post ID

cursorstring required

评论游标/Comment cursor from more.cursor field

sort_type'CONFIDENCE' | 'NEW' | 'TOP' | 'HOT' | 'CONTROVERSIAL' | 'OLD' | 'RANDOM'

排序方式/Sort method: CONFIDENCE, NEW, TOP, HOT, CONTROVERSIAL, OLD, RANDOM

need_formatboolean

是否需要清洗数据/Whether to clean and format the data

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

    • breaking

      the query request parameter sort_type was restricted to a list of enum values

    • breaking

      for the query request parameter cursor, the minLength was increased from 0 to 13

    • breaking

      for the query request parameter post_id, the minLength was increased from 0 to 4

    • breaking

      added the pattern ^commenttree: to the query request parameter cursor

    • breaking

      added the pattern ^t3_[a-z0-9]{1,17}$ to the query request parameter post_id

    • warning

      for the query request parameter cursor, the maxLength was set to 4096

    • warning

      for the query request parameter post_id, the maxLength was set to 20

    • info

      added the new optional query request parameter language

    • info

      added the new enum value CONFIDENCE to the query request parameter sort_type

    • info

      added the new enum value CONTROVERSIAL to the query request parameter sort_type

    • info

      added the new enum value HOT to the query request parameter sort_type

    • info

      added the new enum value NEW to the query request parameter sort_type

    • info

      added the new enum value OLD to the query request parameter sort_type

    • info

      added the new enum value RANDOM to the query request parameter sort_type

    • info

      added the new enum value TOP to the query request parameter sort_type