Skip to main content
POST
Reference example
获取视频号用户作品列表 计费 — 按成功调用计费,最终扣费按你的套餐倍率浮动。仅当上游响应体 code 为 200 时计费。
响应结构尚未完整文档化 —— 以实际调用为准。

示例

请求规范

完整 OpenAPI 定义 有效请求与价格声明(包括认证和引用的 schema):

费用与请求规则

公开参考价格:每次成功请求 $0.01 USD。 最终费用以账户适用价格及实际结算为准。 公开参考值不是你的账户报价或最终扣费。对于支持 X-AISA-Cost-Mode: quote 的接口,执行前请针对完整请求获取免费报价;执行后通过响应费用元数据和 Usage Logs 核对结算费用。1 USD 等于 1,000,000 个整数 micro-USD。
  • 默认请求参考估价(USD): 0.01
  • 计费依据: fixed_success
  • 公开参考倍率: 1.0
  • 结算证据来源: request_snapshot

授权

Authorization
string
header
必填

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

请求体

application/json
username
string
必填

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

Required string length: 10 - 256
Pattern: ^v2_[0-9a-fA-F]+@finder$
示例:

"v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder"

last_buffer
string | null
默认值:""

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

Pattern: ^[A-Za-z0-9+/=_-]*$
raw
boolean
默认值:true

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

响应

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

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

Cache message (ZH-CN)

cache_url
string | null

The URL to access the cached result

code
integer
默认值:200

HTTP 状态码

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
默认值:Request successful. This request will incur a charge.

Response message (EN-US)

message_zh
string
默认值:请求成功,本次请求将被计费。

Response message (ZH-CN)

params
any
默认值:{}

The parameters used in the request

request_id
string | null

Unique request identifier

router
string
默认值:""

The endpoint that generated this response

support
string
默认值: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
默认值:America/Los_Angeles

The timezone of the response time