Get WeChat Channels Video Comments

Get WeChat Channels Video Comments

POST https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_video_comments

Get WeChat Channels Video Comments

cURL

curl --request POST \
  --url https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_video_comments \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "object_id": "14941130915890399732",
  "last_buffer": "",
  "comment_id": "",
  "raw": true
}
'

200

{
  "code": 200,
  "request_id": "<string>",
  "message": "Request successful. This request will incur a charge.",
  "message_zh": "请求成功，本次请求将被计费。",
  "support": "Discord: https://discord.gg/aMEAS8Xsvz",
  "time": "<string>",
  "time_stamp": 123,
  "time_zone": "America/Los_Angeles",
  "docs": "<string>",
  "cache_message": "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_zh": "本次响应已缓存，可通过下方 URL 直接查看，有效期 24 小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。",
  "cache_url": "<string>",
  "router": "",
  "params": {},
  "data": "<unknown>"
}

Get WeChat Channels Video 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

curl -X POST "https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_video_comments" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'  # see request schema below

Authorizations

Authorization · string · header · required

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

Body

application/json

object_id · string · required

Video objectId (numeric), e.g. 14941130915890399732. From the video id of fetch_user_videos / fetch_video_detail.

API references: fetch_user_videos = POST /tikhub/wechat_channels/v2/fetch_user_videos (operationId: post_tikhub_wechat_channels_v2_fetch_user_videos); fetch_video_detail = POST /tikhub/wechat_channels/v2/fetch_video_detail (operationId: post_tikhub_wechat_channels_v2_fetch_video_detail).

Maximum string length: 32

Pattern: ^[0-9]+$

Example:

"14941130915890399732"

last_buffer · string | null · default: ""

Optional pagination cursor (base64). Leave empty for the first page; when down_continue is truthy, pass the previous page's last_buffer.

Pattern: ^[A-Za-z0-9+/=_-]*$

comment_id · string | null · default: ""

Pass a commentId (numeric) to expand its replies, leave empty for first-level comments

Usage: Optional. To expand the replies of a comment, pass its comment_id (numeric); leave empty for the first-level page.

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

• 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.

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.