[中文]

用途:

传直播 live_id 返回直播间详情：主播信息、直播状态、在线人数、回放信息等。

⏱️ 由于微信服务器原因，本接口响应较慢，请将客户端请求超时（timeout）设置为 30 秒；timeout 设置过小会造成已扣费但收不到响应的情况。

⚠️ 大整数 ID 精度：响应中的 live_id 等为 64 位大整数，超出 JavaScript 安全整数范围（2^53-1）。请始终以字符串方式接收 / 传递这类 ID（解析 JSON 用 json-bigint 或按文本取值），勿让其经过 JS Number。Swagger UI 文档页对超大整数会末位舍入显示，属正常现象，不影响接口实际返回的数据。

参数:

live_id: 直播 ID（纯数字）。来源：fetch_live_history 的回放条目、直播入口或直播分享。示例 2078950291205875194。

scene: 可选，进入场景，默认 5。

finder_username: 可选，主播 finder username（v2_…@finder 格式），提高命中。示例 v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder（虎嗅）。

raw: 可选，默认 True。True=原始响应；False=精简解析结构。

直播间详情

响应结构与 JSON Path:

`raw=false`（精简，snake_case）:

$.data.live_id —— 直播 ID；$.data.object_id —— 关联作品 objectId（可能为空串）

$.data.anchor_nickname / $.data.anchor_username / $.data.anchor_head_url —— 主播昵称 / username / 头像

$.data.live_cover_url —— 直播封面

$.data.live_status —— 直播状态（1=直播中 / 2=已结束 …）；$.data.status_desc —— 状态文案（可能为空）

$.data.online_count / $.data.max_online_count —— 当前 / 峰值在线人数（已结束的直播一般为 0）

$.data.replay_status —— 回放状态；$.data.replay_url —— 回放地址（可能为空）；$.data.replay_watch_uv —— 回放观看人数

`raw=true`（完整原始响应，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）→ 主播相关字段

另含 $.data.liveCover、$.data.anchorInfo、$.data.replaySubscribedCount 等几十个原始字段

[English]

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

TikOmni Pricing

Actual billing follows the TikOmni pricing catalog. Query /api/pricing/v1/endpoints with this endpoint path for the current unit price.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Body Params application/jsonRequired

Example

{
    "live_id": "2078950291205875194",
    "scene": 5,
    "finder_username": "v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder",
    "raw": true
}

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

获取视频号直播间详情/Get WeChat Channels Live Detail

[中文]

用途:

参数:

返回:

响应结构与 JSON Path:

`raw=false`（精简，snake_case）:

`raw=true`（完整原始响应，camelCase）:

[English]

Purpose:

Parameters:

Return:

Response structure & JSON Path:

`raw=false` (simplified, snake_case):

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

TikOmni Pricing

Request

Request Code Samples

Responses

获取视频号直播间详情/Get WeChat Channels Live Detail

[中文]#

用途:#

参数:#

返回:#

响应结构与 JSON Path:#

raw=false（精简，snake_case）:#

raw=true（完整原始响应，camelCase）:#

[English]#

Purpose:#

Parameters:#

Return:#

Response structure & JSON Path:#

raw=false (simplified, snake_case):#

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

TikOmni Pricing#

Request

Request Code Samples

Responses

[中文]

用途:

参数:

返回:

响应结构与 JSON Path:

`raw=false`（精简，snake_case）:

`raw=true`（完整原始响应，camelCase）:

[English]

Purpose:

Parameters:

Return:

Response structure & JSON Path:

`raw=false` (simplified, snake_case):

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

TikOmni Pricing