WeChat Get Comment Replies

20.65 credits/call
ae_wechat_get_comment_replies

Retrieve second-level replies under a first-level comment on a WeChat Official Account article. ### Inputs Pass a required `request_body` object containing: - `url` (required): an HTTP(S) article link on `mp.weixin.qq.com/s`, up to 2048 characters. - `content_id` (optional): the target first-level comment's ID, available at `$.data.comments[N].content_id` in an article-comments response. Omit it to select the first comment with replies. Default: empty string. - `comment_id` (optional): the article's comment-section ID. This differs from `content_id`. If already available at `$.data.content.comment_id` in an article-detail response, supplying it can reduce response time. - `offset` (optional): nonnegative integer pagination offset; default `0`. - `raw` (optional): default `true` for full reply objects; `false` for simplified reply objects. Supply nonempty IDs as digit strings of at most 32 characters; the two optional ID fields also accept null. ### Results `$.data.replies` contains the current page of replies. Common reply fields are `reply_id`, `nick_name`, `content` and `create_time`. The simplified view also includes IP region (`ip_wording`), identity label (`identity_name`), AI-reply flag (`from_ai`) and featured flag (`reply_is_elected`). `$.data.content_id` echoes the target comment ID; `parent_nick` is the parent commenter's nickname. `reply_total` is the total number of replies, while `count` is the number returned on this page. `offset`, `next_offset` and `has_more` describe pagination. When `$.data.has_more` is true, use `$.data.next_offset` as the next request's `offset`, keeping the same article and target comment. Replies are not automatically fetched across all pages. Both `raw` modes use the same outer structure; only the detail within each reply object changes. IDs may exceed JavaScript's safe integer range: parse them losslessly and preserve them as strings, never through `Number`. Responses can be slow; set the client request timeout to 30 seconds. This timeout is a client setting, not a tool input.

Social
20.65 credits/call

Pricing

20.65 credits/call
ConditionCharge
Each call20.65 credits/call

20.65 credits/call Charges are per query. A successful query is billed even if it returns no results.

Parameters

Optional parameters use the platform defaults when omitted.

ParameterTypeRequiredDescriptionDefault
request_bodyobjectYes获取公众号文章中某条一级评论下二级回复的请求体对象。包含必填的文章链接 url,以及可选的目标一级评论 content_id、文章评论区 comment_id、翻页偏移 offset 和回复详略选项 raw。/Request body object for retrieving second-level replies beneath a first-level comment on a WeChat Official Account article. Contains the required article URL (url) and optional target first-level comment ID (content_id), article comment-section ID (comment_id), pagination offset (offset), and reply detail option (raw).—
request_body.rawbooleanNoTrue=原始响应;False=精简解析结构/True=raw response; False=simplified parsed structuretrue
request_body.urlstringYes公众号文章链接(https://mp.weixin.qq.com/s/…)/WeChat MP article URL (https://mp.weixin.qq.com/s/…)—
request_body.offsetintegerNo回复翻页偏移,首页 0;has_more=true 时传上次返回的 next_offset/Reply pagination offset, 0 for first page; pass next_offset from the previous response when has_more=true0
request_body.comment_idstring | nullNo文章的评论 id(可选,**性能捷径**):不传时上游要先抓并解析整篇文章 HTML 才能拿到它,约占本接口耗时的一半;已有该值时传进来可显著加快。取自 /fetch_article_detail 或 /fetch_article_detail_h5 响应的 `$.data.content.comment_id`/Article comment id (optional, performance shortcut): when omitted, upstream must fetch and parse the whole article HTML to obtain it, which accounts for about half of this endpoint's latency—
request_body.content_idstring | nullNo目标一级评论的 content_id(纯数字),不传则自动取第一条有回复的评论/content_id (numeric) of the target first-level comment; defaults to the first comment that has replies""

Invocation example

Copy the request and explore its response example.

POST/agent-api/v1/tool/executeX-Api-Key
Request coderequest.sh
curl --request POST \
  --url 'https://agentearth.ai/agent-api/v1/tool/execute?tool_name=ae_wechat_get_comment_replies' \
  --header "X-Api-Key: $AGENTEARTH_API_KEY" \
  --header 'Content-Type: application/json' \
  --data-raw '{
  "params": {
    "request_body": {
      "content_id": "12109128638545265979",
      "offset": 0,
      "raw": false,
      "url": "http://mp.weixin.qq.com/s?__biz=Mzk3NTA0MzM5NA==&mid=2247483745&idx=1&sn=3f34e768cf457a501038991ed30be1f4#rd"
    }
  }
}'
Response exampleresponse.json
JSONPartial content
{
  "code": 200,
  "data": {
    "content_id": "12109128638545265979",
    "count": 10,
    "debug_id": "d2dd8f85",
    "debug_info": "gAAAAABq6_REFJ2SoLkTwsNXp_IMyDUEE9lwDC4_T9xGRTu-BCaaHZznrradBwskatzoZ_GgWq5ej2lbpqpZI8VSZFZk5DmImQDnhffxuGc9sgcATeYE_5WiUFyMq10CIZ6zmJ0T4qgtdOLkLFdEy61MPmXeAHiRUlHOcDWAeV_dUjAuUxsnE3o_wKs9fJVB1SvtaNQjRwPD0deKGXc1knlga02PgSqCi8Z5So7P61FYK45KUV6ZD2j7LTvWdk2G",
    "has_more": true,
    "next_offset": 10
  },
  "docs": "https://api.tikhub.io/#/WeChat-Media-Platform-V2-API/fetch_comment_replies_api_v1_wechat_mp_v2_fetch_comment_replies_post",
  "message": "Request successful. This request will incur a charge."
}

This example shows part of the response. Copied content is valid JSON.