Skip to main content
POST
Reference example
Get WeChat MP Article Comments 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

Request contract

  • Method and path: POST /apis/v1/tikhub/wechat_mp/v2/fetch_article_comments
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/tikhub/wechat_mp/v2/fetch_article_comments
  • Runtime facts: 85ae03121f63417c9ff9d57a0fd59fdc6386fd71e2dc732a002843e6d8979d87
Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

Published reference price: $0.01 USD per successful request. Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.01
  • Cost contract: fixed_success
  • Published reference multiplier: 1.0
  • Settlement evidence source: request_snapshot

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
url
string
required

WeChat MP article URL (https://mp.weixin.qq.com/s/…). E.g. https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw

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

"https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw"

buffer
string | null
default:""

Optional, default empty. Pagination cursor; leave empty for the first page, pass buffer from the previous response for the next page.

Maximum string length: 8192
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

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

Return

  • One page of comments with pagination cursor

Response structure & JSON Path

raw=false (simplified view):

  • data outer level is the page summary; comments[] are simplified comments:
    • $.data.appmsgid: message id
    • $.data.elected_total: total featured comments
    • $.data.total_count: total comments
    • $.data.buffer: next-page cursor (pass back as buffer; empty string at the last page)
    • $.data.has_more: whether there is a next page
    • $.data.comment_id: article comment identifier (internal)
    • $.data.comments[N].content_id: comment id (feed into content_id of fetch_comment_replies)
    • $.data.comments[N].nick_name: commenter nickname
    • $.data.comments[N].content: comment content
    • $.data.comments[N].like_num: like count
    • $.data.comments[N].create_time: comment timestamp
    • $.data.comments[N].ip_wording: IP region (province_name / city_name etc.)
    • $.data.comments[N].is_elected / is_top: featured / pinned flags
    • $.data.comments[N].reply_total: total second-level replies
    • $.data.comments[N].replies[]: reply preview (simplified, see fetch_comment_replies)

raw=true (raw):

  • data outer level same as above (appmsgid / elected_total / total_count / buffer / has_more / comment_id); comments[] are full raw comment objects with more fields (snake_case):
    • $.data.comments[N].content_id: comment id (same as simplified mode, still the value fed into fetch_comment_replies)
    • $.data.comments[N].content / nick_name / like_num / create_time / ip_wording / is_elected / is_top: same names and meanings as raw=false
    • Raw-only extra fields: $.data.comments[N].id (floor number) / openid / identity_type / logo_url (avatar) / like_status / is_from_me / $.data.comments[N].reply_new (with reply_total_cnt / reply_list, corresponding to reply_total / replies of the simplified mode)

API references: fetch_comment_replies = POST /tikhub/wechat_mp/v2/fetch_comment_replies (operationId: post_tikhub_wechat_mp_v2_fetch_comment_replies).

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

code
integer
default:200

HTTP status code

data
any

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.

docs
string | null

Link to the API Swagger documentation for this endpoint

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

Response message (EN-US)

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

Response message (ZH-CN)

params
any
default:{}

The parameters used in the request

request_id
string | null

Unique request identifier

router
string
default:""

The endpoint that generated this response

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