Skip to main content
POST
Reference example
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.
Response structure is not yet fully documented — refer to the actual API response.

Example

Request contract

  • Method and path: POST /apis/v1/tikhub/wechat_channels/v2/fetch_live_detail
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_live_detail
  • Runtime facts: 85ae03121f63417c9ff9d57a0fd59fdc6386fd71e2dc732a002843e6d8979d87
Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

Published reference price: $0.01 USD per successful request. Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.01
  • Cost contract: fixed_success
  • Published reference multiplier: 1.0
  • Settlement evidence source: request_snapshot

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
live_id
string
required

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

Maximum string length: 32
Pattern: ^[0-9]+$
Example:

"2078950291205875194"

finder_username
string | null
default:""

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

Maximum string length: 256
Pattern: ^(v2_[0-9a-fA-F]+@finder)?$
Example:

"v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder"

raw
boolean
default:true

True=raw response; False=simplified parsed structure

scene
integer
default:5

Entry scene, default 5

Required range: 0 <= x <= 1000

Response

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
cache_message
string | null
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.

Cache message (EN-US)

cache_message_zh
string | null
default:本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。

Cache message (ZH-CN)

cache_url
string | null

The URL to access the cached result

code
integer
default:200

HTTP status code

data
any

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.

docs
string | null

Link to the API Swagger documentation for this endpoint

message
string
default:Request successful. This request will incur a charge.

Response message (EN-US)

message_zh
string
default:请求成功,本次请求将被计费。

Response message (ZH-CN)

params
any
default:{}

The parameters used in the request

request_id
string | null

Unique request identifier

router
string
default:""

The endpoint that generated this response

support
string
default:Discord: https://discord.gg/aMEAS8Xsvz

Support message

time
string

The time the response was generated

time_stamp
integer

The timestamp the response was generated

time_zone
string
default:America/Los_Angeles

The timezone of the response time