WeChat-Channels-V2-API

获取视频号作品评论/Get WeChat Channels Video Comments

Changed on

[中文]

用途:

  • 获取作品的一级评论(含 IP 属地 / 点赞数);传 comment_id 则返回该评论下的二级回复。
  • 支持翻页获取更多评论。
  • 价格:0.01$/次
  • ⏱️ 由于微信服务器原因,本接口响应较慢,请将客户端请求超时(timeout)设置为 30 秒;timeout 设置过小会造成已扣费但收不到响应的情况。
  • ⚠️ 大整数 ID 精度:响应中的 comment_id 等为 64 位大整数,超出 JavaScript 安全整数范围(2^53-1)。请始终以字符串方式接收 / 传递这类 ID(解析 JSON 用 json-bigint 或按文本取值),勿让其经过 JS Number。Swagger UI 文档页对超大整数会末位舍入显示,属正常现象,不影响接口实际返回的数据。

参数:

  • object_id: 作品 objectId(纯数字),示例 14941130915890399732。来自 fetch_user_videos / fetch_video_detail 的视频 id。
  • last_buffer: 可选,翻页游标(base64)。首页留空;当响应 down_continue 为真时传上一页的 last_buffer。
  • comment_id: 可选。展开某条评论的二级回复时传该评论的 comment_id(纯数字);首页留空。
  • raw: 可选,默认 True。True=原始响应;False=精简解析结构。

返回:

  • 评论列表及翻页游标

响应结构与 JSON Path:

raw=false(精简):

  • 顶层: $.data.object_id(回显)/ $.data.comment_id(展开回复时回显,否则 null)/ $.data.count(本页评论数)/ $.data.down_continue(是否有下一页)/ $.data.last_buffer(翻页游标)
  • 每条评论 $.data.comments[N]:
    • 评论 ID(展开其二级回复时回传): $.data.comments[N].comment_id
    • 评论人: $.data.comments[N].nickname / .username / .head_url
    • 正文: $.data.comments[N].content
    • 点赞 / 回复数: $.data.comments[N].like_count / .reply_count
    • 时间 / IP 属地: $.data.comments[N].create_time / .ip_region

raw=true(原始):

  • 状态码: $.data.baseResponse.ret
  • 评论数组(camelCase): $.data.commentInfo[N],关键字段 commentId / nickname / username / content / likeCount / createtime / headUrl / ipRegionInfo.regionText
  • 翻页: $.data.downContinueFlag、$.data.lastBuffer(另附别名 $.data.last_buffer)
  • 全局计数: $.data.monotonicData.commentCount.commentCount、$.data.countInfo(likeCount/favCount/forwardCount 等)
  • 对应关系: raw=false 的 comments[] 对应 raw=true 的 commentInfo[]。

[English]

Purpose:

  • Get first-level comments of a video (with IP region / like count); pass comment_id to get second-level replies under that comment.
  • Supports pagination for more comments.
  • Price: $0.01 per request
  • ⏱️ Due to WeChat server latency, this endpoint responds slowly; please set your client request timeout to 30 seconds — a timeout that is too small may result in being billed without receiving the response.
  • ⚠️ Large-integer ID precision: IDs such as comment_id in the response are 64-bit big integers beyond JavaScript's safe-integer range (2^53-1). Always receive / pass such IDs as strings (parse JSON with json-bigint or read them as text), never through JS Number. Swagger UI rounds the trailing digits of huge integers in its docs view — this is expected and does not affect the actual data returned by the API.

Parameters:

  • object_id: Video objectId (numeric), e.g. 14941130915890399732. From the video id of fetch_user_videos / fetch_video_detail.
  • last_buffer: Optional pagination cursor (base64). Leave empty for the first page; when down_continue is truthy, pass the previous page's last_buffer.
  • comment_id: Optional. To expand the replies of a comment, pass its comment_id (numeric); leave empty for the first-level page.
  • raw: Optional, default True. True=raw response; False=simplified parsed structure.

Return:

  • Comment list with pagination cursor

Response structure & JSON Path:

raw=false (simplified):

  • Top level: $.data.object_id (echo) / $.data.comment_id (echo when expanding replies, otherwise null) / $.data.count (comments on this page) / $.data.down_continue (has next page) / $.data.last_buffer (pagination cursor)
  • Each comment $.data.comments[N]:
    • Comment ID (pass it back to expand its replies): $.data.comments[N].comment_id
    • Commenter: $.data.comments[N].nickname / .username / .head_url
    • Content: $.data.comments[N].content
    • Like / reply counts: $.data.comments[N].like_count / .reply_count
    • Time / IP region: $.data.comments[N].create_time / .ip_region

raw=true (raw):

  • Status code: $.data.baseResponse.ret
  • Comment array (camelCase): $.data.commentInfo[N], key fields commentId / nickname / username / content / likeCount / createtime / headUrl / ipRegionInfo.regionText
  • Pagination: $.data.downContinueFlag, $.data.lastBuffer (alias $.data.last_buffer also provided)
  • Global counts: $.data.monotonicData.commentCount.commentCount, $.data.countInfo (likeCount/favCount/forwardCount etc.)
  • Mapping: comments[] of raw=false corresponds to commentInfo[] of raw=true.
post/api/v1/wechat_channels/v2/fetch_video_comments

Request

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

Request body

object_idstring required

作品 objectId(纯数字)/Video objectId (numeric)

last_bufferstring nullable

翻页游标(base64),首页留空/Pagination cursor (base64), leave empty for first page

comment_idstring nullable

展开某条评论的二级回复时传其 commentId(纯数字),首页留空/Pass a commentId (numeric) to expand its replies, leave empty for first-level comments

rawboolean

True=原始响应;False=精简解析结构/True=raw response; False=simplified parsed structure

Example request

{
  "object_id": "14941130915890399732"
}

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