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

> Get WeChat Channels Live Detail

Get WeChat Channels Live 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_channels/v2/fetch_live_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_channels/v2/fetch_live_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_channels/v2/fetch_live_detail:
    post:
      tags:
        - TikHub - Wechat_channels
      summary: Get WeChat Channels Live Detail
      description: >-
        WeChat Channels (v2). Pricing and billing notes describe the upstream
        provider. Use the AIsa price quote for gateway calls.


        ### Purpose

        - Pass a live `live_id` to get live-room detail: anchor info, live
        status, online count, replay info, etc.

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

        - live_id: Live ID (numeric). Source: replay items of
        `fetch_live_history`, live entry, or live share. E.g.
        `2078950291205875194`.

        - scene: Optional, entry scene, default 5.

        - finder_username: Optional, anchor finder username (`v2_…@finder`
        format), improves hit rate. E.g.
        `v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder`
        (Huxiu).

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


        ### Return

        - Live room detail


        ### Response structure & JSON Path

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

        - `$.data.live_id` — live ID; `$.data.object_id` — associated video
        objectId (may be empty string)

        - `$.data.anchor_nickname` / `$.data.anchor_username` /
        `$.data.anchor_head_url` — anchor nickname / username / avatar

        - `$.data.live_cover_url` — live cover

        - `$.data.live_status` — live status (1=live / 2=ended …);
        `$.data.status_desc` — status text (may be empty)

        - `$.data.online_count` / `$.data.max_online_count` — current / peak
        online count (usually 0 for ended lives)

        - `$.data.replay_status` — replay status; `$.data.replay_url` — replay
        address (may be empty); `$.data.replay_watch_uv` — replay viewer count

        #### `raw=true` (full raw response, camelCase):

        - `$.data.liveInfo.liveId` → `live_id`; `$.data.liveInfo.objectId` →
        `object_id`

        - `$.data.liveInfo.liveStatus` → `live_status`;
        `$.data.liveInfo.statusDesc` → `status_desc`

        - `$.data.liveInfo.onlineCnt` → `online_count`;
        `$.data.liveInfo.maxOnlineCount` → `max_online_count`

        - `$.data.liveInfo.replayStatus` → `replay_status`;
        `$.data.liveInfo.replayUrl` → `replay_url`

        - `$.data.liveInfo.replayInfo.watchUv` → `replay_watch_uv`

        - `$.data.anchorContact` (`nickname` / `username` / `headUrl` /
        `coverImgUrl` / `liveCoverImgUrl`) → anchor-related fields

        - Also dozens of raw fields like `$.data.liveCover`,
        `$.data.anchorInfo`, `$.data.replaySubscribedCount`


        API references: `fetch_live_history` = `POST
        /tikhub/wechat_channels/v2/fetch_live_history` (operationId:
        `post_tikhub_wechat_channels_v2_fetch_live_history`).
      operationId: post_tikhub_wechat_channels_v2_fetch_live_detail
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FetchLiveDetailRequest'
        required: true
      responses:
        '200':
          description: >-
            Successful response. The outer object follows `ResponseModel`; the
            endpoint-specific payload is in `data`.


            ### Return

            - Live room detail


            ### Response structure & JSON Path

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

            - `$.data.live_id` — live ID; `$.data.object_id` — associated video
            objectId (may be empty string)

            - `$.data.anchor_nickname` / `$.data.anchor_username` /
            `$.data.anchor_head_url` — anchor nickname / username / avatar

            - `$.data.live_cover_url` — live cover

            - `$.data.live_status` — live status (1=live / 2=ended …);
            `$.data.status_desc` — status text (may be empty)

            - `$.data.online_count` / `$.data.max_online_count` — current / peak
            online count (usually 0 for ended lives)

            - `$.data.replay_status` — replay status; `$.data.replay_url` —
            replay address (may be empty); `$.data.replay_watch_uv` — replay
            viewer count

            #### `raw=true` (full raw response, camelCase):

            - `$.data.liveInfo.liveId` → `live_id`; `$.data.liveInfo.objectId` →
            `object_id`

            - `$.data.liveInfo.liveStatus` → `live_status`;
            `$.data.liveInfo.statusDesc` → `status_desc`

            - `$.data.liveInfo.onlineCnt` → `online_count`;
            `$.data.liveInfo.maxOnlineCount` → `max_online_count`

            - `$.data.liveInfo.replayStatus` → `replay_status`;
            `$.data.liveInfo.replayUrl` → `replay_url`

            - `$.data.liveInfo.replayInfo.watchUv` → `replay_watch_uv`

            - `$.data.anchorContact` (`nickname` / `username` / `headUrl` /
            `coverImgUrl` / `liveCoverImgUrl`) → anchor-related fields

            - Also dozens of raw fields like `$.data.liveCover`,
            `$.data.anchorInfo`, `$.data.replaySubscribedCount`
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
components:
  schemas:
    FetchLiveDetailRequest:
      properties:
        live_id:
          type: string
          maxLength: 32
          pattern: ^[0-9]+$
          title: Live Id
          description: >-
            Live ID (numeric). Source: replay items of `fetch_live_history`,
            live entry, or live share. E.g. `2078950291205875194`.


            API references: `fetch_live_history` = `POST
            /tikhub/wechat_channels/v2/fetch_live_history` (operationId:
            `post_tikhub_wechat_channels_v2_fetch_live_history`).
          example: '2078950291205875194'
        scene:
          type: integer
          maximum: 1000
          minimum: 0
          title: Scene
          description: Entry scene, default 5
          default: 5
        finder_username:
          title: Finder Username
          description: >-
            Optional, anchor finder username (`v2_…@finder` format), improves
            hit rate. E.g.
            `v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder`
            (Huxiu).
          default: ''
          example: >-
            v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder
          nullable: true
          type: string
          maxLength: 256
          pattern: ^(v2_[0-9a-fA-F]+@finder)?$
        raw:
          type: boolean
          title: Raw
          description: True=raw response; False=simplified parsed structure
          default: true
      type: object
      required:
        - live_id
      title: FetchLiveDetailRequest
    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.