> ## 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 MP Article Comments

> Get WeChat MP Article Comments

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

<Note>
  Response structure is not yet fully documented — **refer to the actual API response**.
</Note>

## Example

```bash theme={null}
curl -X POST "https://api.aisa.one/apis/v1/tikhub/wechat_mp/v2/fetch_article_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_mp/v2/fetch_article_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_mp/v2/fetch_article_comments:
    post:
      tags:
        - TikHub - Wechat_mp
      summary: Get WeChat MP Article Comments
      description: >-
        WeChat Official Accounts (v2). Pricing and billing notes describe the
        upstream provider. Use the AIsa price quote for gateway calls.


        ### Purpose

        - Get WeChat MP article comments (single page, `buffer` cursor
        pagination); returns one page of featured comments.

        - **Pagination**: leave `buffer` empty for the first page → take
        `buffer` from the response → pass it back in the next request;
        `has_more` false means the last page.

        - For second-level replies of a specific comment, use
        `fetch_comment_replies` (pass the comment's `content_id`).

        - ⏱️ 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 `content_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

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

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

        - raw: Optional, default True. True=full raw comment objects;
        False=simplified comment view.


        ### 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`).
      operationId: post_tikhub_wechat_mp_v2_fetch_article_comments
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FetchArticleCommentsRequest'
        required: true
      responses:
        '200':
          description: >-
            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`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
components:
  schemas:
    FetchArticleCommentsRequest:
      properties:
        url:
          type: string
          maxLength: 2048
          pattern: ^https?://mp\.weixin\.qq\.com/s([/?].+)?$
          title: Url
          description: >-
            WeChat MP article URL (`https://mp.weixin.qq.com/s/…`). E.g.
            `https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw`
          example: https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw
        buffer:
          title: Buffer
          description: >-
            Optional, default empty. Pagination cursor; leave empty for the
            first page, pass `buffer` from the previous response for the next
            page.
          default: ''
          nullable: true
          type: string
          maxLength: 8192
        comment_id:
          title: Comment Id
          description: >-
            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
          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:
        - url
      title: FetchArticleCommentsRequest
    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.