> ## Documentation Index > Fetch the complete documentation index at: https://aisa.one/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get WeChat Channels Video Comments > Get WeChat Channels Video Comments 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 ```bash theme={null} 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 ``` ## OpenAPI ````yaml openapi/tikhub.json POST /tikhub/wechat_channels/v2/fetch_video_comments openapi: 3.0.0 info: title: TikHub API description: >- Multi-platform social media data — Douyin, TikTok, Bilibili, Kuaishou, Weibo, Xiaohongshu, Zhihu, and commercial (Xingtu/Huahuo/Billboard) endpoints. version: 1.0.0 servers: - url: https://api.aisa.one/apis/v1 security: - bearerAuth: [] paths: /tikhub/wechat_channels/v2/fetch_video_comments: post: tags: - TikHub - Wechat_channels summary: Get WeChat Channels Video Comments description: >- WeChat Channels (v2). Pricing and billing notes describe the upstream provider. Use the AIsa price quote for gateway calls. ### 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. - ⏱️ 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. 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`). operationId: post_tikhub_wechat_channels_v2_fetch_video_comments requestBody: content: application/json: schema: $ref: '#/components/schemas/FetchVideoCommentsRequest' required: true responses: '200': description: >- 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. content: application/json: schema: $ref: '#/components/schemas/ResponseModel' components: schemas: FetchVideoCommentsRequest: properties: object_id: type: string maxLength: 32 pattern: ^[0-9]+$ title: Object Id description: >- 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`). example: '14941130915890399732' last_buffer: title: Last Buffer description: >- Optional pagination cursor (base64). **Leave empty for the first page**; when `down_continue` is truthy, pass the previous page's `last_buffer`. default: '' nullable: true type: string pattern: ^[A-Za-z0-9+/=_-]*$ comment_id: title: Comment Id description: >- 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. default: '' nullable: true type: string maxLength: 32 pattern: ^[0-9]*$ raw: type: boolean title: Raw description: True=raw response; False=simplified parsed structure default: true type: object required: - object_id title: FetchVideoCommentsRequest ResponseModel: properties: code: type: integer title: Code description: HTTP status code default: 200 request_id: title: Request Id description: Unique request identifier nullable: true type: string message: type: string title: Message description: Response message (EN-US) default: Request successful. This request will incur a charge. message_zh: type: string title: Message Zh description: Response message (ZH-CN) default: 请求成功，本次请求将被计费。 support: type: string title: Support description: Support message default: 'Discord: https://discord.gg/aMEAS8Xsvz' time: type: string title: Time description: The time the response was generated time_stamp: type: integer title: Time Stamp description: The timestamp the response was generated time_zone: type: string title: Time Zone description: The timezone of the response time default: America/Los_Angeles docs: title: Docs description: Link to the API Swagger documentation for this endpoint nullable: true type: string cache_message: title: Cache Message description: Cache message (EN-US) 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. nullable: true type: string cache_message_zh: title: Cache Message Zh description: Cache message (ZH-CN) default: >- 本次响应已缓存，可通过下方 URL 直接查看，有效期 24 小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。 nullable: true type: string cache_url: title: Cache Url description: The URL to access the cached result nullable: true type: string router: type: string title: Router description: The endpoint that generated this response default: '' params: title: Params description: The parameters used in the request default: {} data: title: Data description: >- 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. nullable: true type: object title: ResponseModel securitySchemes: bearerAuth: type: http scheme: bearer description: AIsa API key. Get yours at https://aisa.one ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.