Skip to main content
POST
wechat_channels fetch_video_detail
Get WeChat Channels Video 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_video_detail
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_video_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
export_id
string | null
default:""

Second priority, optional. exportId from search results (must start with export/). Search results often only carry exportId without a plain object_id — pass export_id directly in that case (it expires, use it soon).

Maximum string length: 2048
Pattern: ^(export/.+)?$
object_id
string | null
default:""

Highest priority, optional. Video objectId (numeric), e.g. 14941130915890399732. Obtainable from the video id of fetch_user_videos / fetch_collection_videos.

API references: fetch_collection_videos = POST /tikhub/wechat_channels/v2/fetch_collection_videos (operationId: post_tikhub_wechat_channels_v2_fetch_collection_videos); fetch_user_videos = POST /tikhub/wechat_channels/v2/fetch_user_videos (operationId: post_tikhub_wechat_channels_v2_fetch_user_videos).

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

"14941130915890399732"

object_nonce_id
string | null
default:""

Optional objectNonceId (numeric, improves hit rate

Usage: Optional. feedNonceId (numeric) from search results, pairs with the above to improve hit rate.

Maximum string length: 32
Pattern: ^[0-9]*$
raw
boolean
default:true

True=raw response; False=simplified parsed structure (recommended for media download

share_url
string | null
default:""

Last, optional. Channels share URL (https://weixin.qq.com/sph/…), e.g. https://weixin.qq.com/sph/AH3sCoIPhH. Used only when both object_id and export_id are empty.

Maximum string length: 256
Pattern: ^(https?://weixin\.qq\.com/sph/[A-Za-z0-9]+/?)?$

Response

Successful response. The outer object follows ResponseModel; the endpoint-specific payload is in data.

Return

  • Full video detail (including media download address and decryption key)

Response structure & JSON Path

raw=false (simplified, recommended):

  • data is a single video object:
    • id (video objectId): $.data.id
    • username (v2_…@finder) / nickname / title: $.data.username etc.
    • Interaction counts: $.data.read_count / .like_count / .fav_count / .forward_count / .comment_count
    • Publish time / type / location: $.data.create_time / $.data.object_type / $.data.location
    • Media object: $.data.media (see download/decryption below)

raw=true (raw):

  • Status code: $.data.baseResponse.ret
  • Hit receipt: $.data.objectResponses[0].objectId / .exportId
  • Video object (note: plural objects, camelCase): $.data.objects[0]
  • Mapping: flat fields of raw=false correspond to objects[0] of raw=true.
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