> ## 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 Detail

> Get WeChat MP Article Detail

Get WeChat MP Article Detail

**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_detail" \
  -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_detail
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_detail:
    post:
      tags:
        - TikHub - Wechat_mp
      summary: Get WeChat MP Article Detail
      description: >-
        WeChat Official Accounts (v2). Pricing and billing notes describe the
        upstream provider. Use the AIsa price quote for gateway calls.


        ### Purpose

        - Pass an article URL to get the article body / title / author / cover /
        publish time / album info.

        - Regardless of `raw`, the nested `content` JSON string is always parsed
        into an object (structure normalized); `raw` only controls the
        projection scope of outer fields.

        - ⏱️ 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` / `msgId` 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/…` or long URL
        with `__biz`). E.g. `https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw`

        - raw: Optional, default True. True=raw response; False=simplified
        projection.


        ### Return

        - Article detail (body / title / author / cover / publish time / album
        info)


        ### Response structure & JSON Path

        #### `raw=false` (simplified projection):

        - `data` has only 4 top-level fields; the article body is aggregated in
        `content`:
            - `$.data.url`: article URL
            - `$.data.bizUin`: official account bizUin (int)
            - `$.data.itemIdx`: article position index
            - `$.data.content`: parsed body object, common paths:
                - `$.data.content.title`: title
                - `$.data.content.nick_name` / `$.data.content.user_name`: account name / gh_username
                - `$.data.content.author`: author
                - `$.data.content.desc`: digest
                - `$.data.content.create_time`: publish time (text like `"2025-03-05 12:22"`)
                - `$.data.content.ori_create_time`: publish timestamp (int seconds)
                - `$.data.content.cdn_url`: cover image
                - `$.data.content.comment_id`: comment id (internal id fed into comment endpoints)
                - `$.data.content.appmsgalbuminfo`: album info (`album_id` / `title` / prev & next links)
                - `$.data.content.content_text`: plain text extracted from the body HTML
        #### `raw=true` (raw):

        - `data` is the full item (all fields of `raw=false`, plus template /
        cache / time metadata):
            - `$.data.url` / `$.data.bizUin` / `$.data.itemIdx`: same as simplified mode
            - `$.data.msgId`: message id
            - `$.data.lastModifyTime`: last modified timestamp
            - `$.data.tmplVersion` / `$.data.tmplVersions[]`: H5 template versions
            - `$.data.clientCacheTime`: client cache seconds
            - `$.data.content.*`: same structure as `content` of `raw=false` (also includes `content_text`)
      operationId: post_tikhub_wechat_mp_v2_fetch_article_detail
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FetchArticleDetailRequest'
        required: true
      responses:
        '200':
          description: >-
            Successful response. The outer object follows `ResponseModel`; the
            endpoint-specific payload is in `data`.


            ### Return

            - Article detail (body / title / author / cover / publish time /
            album info)


            ### Response structure & JSON Path

            #### `raw=false` (simplified projection):

            - `data` has only 4 top-level fields; the article body is aggregated
            in `content`:
                - `$.data.url`: article URL
                - `$.data.bizUin`: official account bizUin (int)
                - `$.data.itemIdx`: article position index
                - `$.data.content`: parsed body object, common paths:
                    - `$.data.content.title`: title
                    - `$.data.content.nick_name` / `$.data.content.user_name`: account name / gh_username
                    - `$.data.content.author`: author
                    - `$.data.content.desc`: digest
                    - `$.data.content.create_time`: publish time (text like `"2025-03-05 12:22"`)
                    - `$.data.content.ori_create_time`: publish timestamp (int seconds)
                    - `$.data.content.cdn_url`: cover image
                    - `$.data.content.comment_id`: comment id (internal id fed into comment endpoints)
                    - `$.data.content.appmsgalbuminfo`: album info (`album_id` / `title` / prev & next links)
                    - `$.data.content.content_text`: plain text extracted from the body HTML
            #### `raw=true` (raw):

            - `data` is the full item (all fields of `raw=false`, plus template
            / cache / time metadata):
                - `$.data.url` / `$.data.bizUin` / `$.data.itemIdx`: same as simplified mode
                - `$.data.msgId`: message id
                - `$.data.lastModifyTime`: last modified timestamp
                - `$.data.tmplVersion` / `$.data.tmplVersions[]`: H5 template versions
                - `$.data.clientCacheTime`: client cache seconds
                - `$.data.content.*`: same structure as `content` of `raw=false` (also includes `content_text`)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
components:
  schemas:
    FetchArticleDetailRequest:
      properties:
        url:
          type: string
          maxLength: 2048
          pattern: ^https?://mp\.weixin\.qq\.com/s([/?].+)?$
          title: Url
          description: … or long URL with __biz
          example: https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw
        raw:
          type: boolean
          title: Raw
          description: True=raw response; False=simplified parsed structure
          default: true
      type: object
      required:
        - url
      title: FetchArticleDetailRequest
    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.