> ## 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 User Videos

> Get WeChat Channels User Videos

Get WeChat Channels User Videos

**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_channels/v2/fetch_user_videos" \
  -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_user_videos
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_user_videos:
    post:
      tags:
        - TikHub - Wechat_channels
      summary: Get WeChat Channels User Videos
      description: >-
        WeChat Channels (v2). Pricing and billing notes describe the upstream
        provider. Use the AIsa price quote for gateway calls.


        ### Purpose

        - Get the video list from a WeChat Channels account's homepage.

        - Each video carries a `media` object (`url` / `url_token` / `full_url`
        / `decode_key`) ready for download and decryption.

        - Supports pagination for more videos.

        - ⏱️ 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 `id` / `object_nonce_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

        - username: WeChat Channels finder username (`v2_…@finder` format), e.g.
        `v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder`
        (People's Daily). See `fetch_channel_info` / `fetch_video_detail` /
        `fetch_channel_id_to_username` docs for how to obtain it.

        - last_buffer: Optional pagination cursor (base64). **Leave empty for
        the first page**; when `up_continue` in the response is truthy, pass the
        previous page's `last_buffer` to get the next page. (base64 contains
        `+//=` characters, hence body instead of query.)

        - raw: Optional, default True. True=raw response; False=simplified
        parsed structure (recommended for media download).


        ### Return

        - User video list with pagination cursor


        ### Response structure & JSON Path

        #### `raw=false` (simplified, recommended):

        - Top level: `$.data.username` / `$.data.nickname` / `$.data.count`
        (videos on this page) / `$.data.up_continue` (has next page) /
        `$.data.last_buffer` (pagination cursor)

        - Each video `$.data.videos[N]` (N is the index):
            - `id` (video objectId, feed into `fetch_video_detail` / `fetch_video_comments`): `$.data.videos[N].id`
            - `object_nonce_id`: `$.data.videos[N].object_nonce_id`
            - `username` / `nickname` / `title`: `$.data.videos[N].username` etc.
            - Interaction counts: `$.data.videos[N].read_count` / `.like_count` / `.fav_count` / `.forward_count` / `.comment_count`
            - Publish time: `$.data.videos[N].create_time`
            - Location: `$.data.videos[N].location`
        #### `raw=true` (raw):

        - Status code: `$.data.baseResponse.ret`

        - Video array (note: singular **`object`**, camelCase):
        `$.data.object[N]`

        - Pagination: `$.data.upContinueFlag`, `$.data.lastBuffer` (alias
        `$.data.last_buffer` also provided)

        - Account profile: `$.data.contact` (nickname/signature/`authInfo`
        etc.), `$.data.finderUserInfo`

        - Mapping: `videos[]` of raw=false corresponds to `object[]` of
        raw=true; `nickname` comes from `finderUserInfo` / `contact.nickname`.


        ### Important Note (video download & decryption)

        - Accessing the `url` field directly may fail to open the video page —
        WeChat Channels uses **anti-hotlinking**. Concatenate `url` and
        `url_token` into a full URL and download via any HTTP client (opening =
        HTTP 200, **does not mean playable**, the file is encrypted).

        - ⚠️ **Video Encryption Notice**: If the downloaded MP4 cannot be
        played, it is encrypted. Use the `decode_key` field from the response
        together with the encrypted file to decrypt it.

        - ⚠️ **Important**: WeChat returns a **new encrypted link and
        `decode_key` on every request** (even for the same video). Make sure the
        `decode_key` and the downloaded encrypted file come from the **same API
        response**, otherwise decryption will fail.

        - JSON Path (per video — N is the index):
            - `raw=false` (**recommended for media download**) — `$.data.videos[N].media` is a single object:
                - Video CDN link (without Token): `$.data.videos[N].media.url`
                - Token of the video CDN link: `$.data.videos[N].media.url_token`
                - Pre-concatenated full CDN URL (= url + url_token, ready to use): `$.data.videos[N].media.full_url`
                - Video decryption key (different on every request): `$.data.videos[N].media.decode_key`
            - `raw=true` — media is nested at `$.data.object[N].objectDesc.media[0]` (camelCase: `url` / `urlToken` / `decodeKey`, full URL = `url` + `urlToken`). For media download, prefer `raw=false` for cleaner paths.
        - Online decryption tool:
        https://evil0ctal.github.io/WeChat-Channels-Video-File-Decryption/

        - Self-deployable decryption API (one-click Docker deployment):
        https://github.com/Evil0ctal/WeChat-Channels-Video-File-Decryption


        API references: `fetch_channel_id_to_username` = `POST
        /tikhub/wechat_channels/v2/fetch_channel_id_to_username` (operationId:
        `post_tikhub_wechat_channels_v2_fetch_channel_id_to_username`);
        `fetch_channel_info` = `POST
        /tikhub/wechat_channels/v2/fetch_channel_info` (operationId:
        `post_tikhub_wechat_channels_v2_fetch_channel_info`);
        `fetch_video_comments` = `POST
        /tikhub/wechat_channels/v2/fetch_video_comments` (operationId:
        `post_tikhub_wechat_channels_v2_fetch_video_comments`);
        `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_user_videos
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FetchUserVideosRequest'
        required: true
      responses:
        '200':
          description: >-
            Successful response. The outer object follows `ResponseModel`; the
            endpoint-specific payload is in `data`.


            ### Return

            - User video list with pagination cursor


            ### Response structure & JSON Path

            #### `raw=false` (simplified, recommended):

            - Top level: `$.data.username` / `$.data.nickname` / `$.data.count`
            (videos on this page) / `$.data.up_continue` (has next page) /
            `$.data.last_buffer` (pagination cursor)

            - Each video `$.data.videos[N]` (N is the index):
                - `id` (video objectId, feed into `fetch_video_detail` / `fetch_video_comments`): `$.data.videos[N].id`
                - `object_nonce_id`: `$.data.videos[N].object_nonce_id`
                - `username` / `nickname` / `title`: `$.data.videos[N].username` etc.
                - Interaction counts: `$.data.videos[N].read_count` / `.like_count` / `.fav_count` / `.forward_count` / `.comment_count`
                - Publish time: `$.data.videos[N].create_time`
                - Location: `$.data.videos[N].location`
            #### `raw=true` (raw):

            - Status code: `$.data.baseResponse.ret`

            - Video array (note: singular **`object`**, camelCase):
            `$.data.object[N]`

            - Pagination: `$.data.upContinueFlag`, `$.data.lastBuffer` (alias
            `$.data.last_buffer` also provided)

            - Account profile: `$.data.contact` (nickname/signature/`authInfo`
            etc.), `$.data.finderUserInfo`

            - Mapping: `videos[]` of raw=false corresponds to `object[]` of
            raw=true; `nickname` comes from `finderUserInfo` /
            `contact.nickname`.


            API references: `fetch_video_comments` = `POST
            /tikhub/wechat_channels/v2/fetch_video_comments` (operationId:
            `post_tikhub_wechat_channels_v2_fetch_video_comments`);
            `fetch_video_detail` = `POST
            /tikhub/wechat_channels/v2/fetch_video_detail` (operationId:
            `post_tikhub_wechat_channels_v2_fetch_video_detail`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
components:
  schemas:
    FetchUserVideosRequest:
      properties:
        username:
          type: string
          maxLength: 256
          minLength: 10
          pattern: ^v2_[0-9a-fA-F]+@finder$
          title: Username
          description: >-
            WeChat Channels finder username (`v2_…@finder` format), e.g.
            `v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder`
            (People's Daily). See `fetch_channel_info` / `fetch_video_detail` /
            `fetch_channel_id_to_username` docs for how to obtain it.


            API references: `fetch_channel_id_to_username` = `POST
            /tikhub/wechat_channels/v2/fetch_channel_id_to_username`
            (operationId:
            `post_tikhub_wechat_channels_v2_fetch_channel_id_to_username`);
            `fetch_channel_info` = `POST
            /tikhub/wechat_channels/v2/fetch_channel_info` (operationId:
            `post_tikhub_wechat_channels_v2_fetch_channel_info`);
            `fetch_video_detail` = `POST
            /tikhub/wechat_channels/v2/fetch_video_detail` (operationId:
            `post_tikhub_wechat_channels_v2_fetch_video_detail`).
          example: >-
            v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder
        last_buffer:
          title: Last Buffer
          description: >-
            Optional pagination cursor (base64). **Leave empty for the first
            page**; when `up_continue` in the response is truthy, pass the
            previous page's `last_buffer` to get the next page. (base64 contains
            `+//=` characters, hence body instead of query.)
          default: ''
          nullable: true
          type: string
          pattern: ^[A-Za-z0-9+/=_-]*$
        raw:
          type: boolean
          title: Raw
          description: >-
            True=raw response; False=simplified parsed structure (recommended
            for media download
          default: true
      type: object
      required:
        - username
      title: FetchUserVideosRequest
    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.