Skip to main content
POST
Get WeChat MP Comment Replies
Get WeChat MP Comment Replies Pricing — billed per successful call; the final charge scales by your plan multiplier. Charged only when the upstream response body code is 200.
Response structure is not yet fully documented — refer to the actual API response.

Example

Authorizations

Authorization
string
header
required

AIsa API key. Get yours at https://aisa.one

Body

application/json
url
string
required

WeChat MP article URL (https://mp.weixin.qq.com/s/…). E.g. http://mp.weixin.qq.com/s?__biz=Mzk3NTA0MzM5NA==&mid=2247483745&idx=1&sn=3f34e768cf457a501038991ed30be1f4#rd

Maximum string length: 2048
Pattern: ^https?://mp\.weixin\.qq\.com/s([/?].+)?$
Example:

"http://mp.weixin.qq.com/s?__biz=Mzk3NTA0MzM5NA==&mid=2247483745&idx=1&sn=3f34e768cf457a501038991ed30be1f4#rd"

content_id
string | null
default:""

Optional (numeric). content_id of the target first-level comment, from $.data.comments[N].content_id of the fetch_article_comments response; defaults to the first comment that has replies when omitted. E.g. 12109128638545265979

API references: fetch_article_comments = POST /tikhub/wechat_mp/v2/fetch_article_comments (operationId: post_tikhub_wechat_mp_v2_fetch_article_comments).

Maximum string length: 32
Pattern: ^[0-9]*$
Example:

"12109128638545265979"

offset
integer
default:0

Optional, default 0 (>=0). Reply pagination offset; 0 for the first page, pass next_offset from the previous response when has_more=true.

Required range: x >= 0
comment_id
string | null

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

Maximum string length: 32
Pattern: ^[0-9]*$
raw
boolean
default:true

True=raw response; False=simplified parsed structure

Response

200 - application/json

Successful response. The outer object follows ResponseModel; the endpoint-specific payload is in data.

Return

  • Second-level reply list with pagination info

Note: the outer structure is identical for raw=true and raw=false; the difference is only in the field granularity of each replies[] element (simplified view vs full raw object).

Response structure & JSON Path

raw=false (simplified replies):

  • $.data.content_id: target comment id (echo)
  • $.data.parent_nick: nickname of the parent comment (the one replied to)
  • $.data.reply_total: total second-level replies
  • $.data.count: number of replies returned this time
  • $.data.replies[N].reply_id: reply id
  • $.data.replies[N].nick_name: replier nickname
  • $.data.replies[N].content: reply content
  • $.data.replies[N].create_time: reply timestamp
  • $.data.replies[N].ip_wording: IP region
  • $.data.replies[N].identity_name: identity label
  • $.data.replies[N].from_ai / reply_is_elected: AI reply / featured flags
  • Pagination fields: $.data.offset / $.data.next_offset / $.data.has_more

raw=true (raw):

  • Outer content_id / parent_nick / reply_total / count (and offset / next_offset / has_more in single-page mode) are identical to raw=false; the only difference is that replies[] elements are full raw reply objects (including fields projected away in raw=false). Common paths remain $.data.replies[N].content / $.data.replies[N].reply_id / $.data.replies[N].nick_name.
code
integer
default:200

HTTP status code

request_id
string | null

Unique request identifier

message
string
default:Request successful. This request will incur a charge.

Response message (EN-US)

message_zh
string
default:请求成功,本次请求将被计费。

Response message (ZH-CN)

support
string
default:Discord: https://discord.gg/aMEAS8Xsvz

Support message

time
string

The time the response was generated

time_stamp
integer

The timestamp the response was generated

time_zone
string
default:America/Los_Angeles

The timezone of the response time

docs
string | null

Link to the API Swagger documentation for this endpoint

cache_message
string | null
default: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.

Cache message (EN-US)

cache_message_zh
string | null
default:本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。

Cache message (ZH-CN)

cache_url
string | null

The URL to access the cached result

router
string
default:""

The endpoint that generated this response

params
any
default:{}

The parameters used in the request

data
any | null

Endpoint-specific response payload. The official shared model does not declare a fixed type or field set. Use the operation's documented return fields or response example; an operation-specific schema, when present, describes the documented fields. Undocumented fields must be read from the actual response rather than assumed.