Skip to main content
POST
wechat_channels fetch_search_channel_videos
Search Videos Within a WeChat Channel 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_search_channel_videos
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_search_channel_videos
  • 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
keyword
string
required

Keyword to search within this channel (1-100 chars

Required string length: 1 - 100
Example:

"news"

username
string
required

Creator finder username (v2_…@finder format

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

"v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder"

cursor
string | null

Pagination cursor. Leave empty for the first page, then pass the previous response next_cursor verbatim. The cursor is opaque; do not parse or concatenate it.

Maximum string length: 4096
raw
boolean
default:true

True=raw response; False=simplified parsed structure

Response

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

Return

  • In-channel search hit list

Response structure & JSON Path

raw=false (simplified, snake_case):

  • $.data.username / $.data.keyword — input echo
  • $.data.count — hits on this page (e.g. 20)
  • $.data.items[] — hit array, per item (N is the index):
    • $.data.items[N].type — result type (e.g. video)
    • $.data.items[N].doc_id — document id
    • $.data.items[N].title — title (search highlight markers stripped)
    • $.data.items[N].desc / .thumb_url / .username / .nickname — description / thumbnail / author (may be null for some items)
  • $.data.continue_flag — has more (1=yes)
  • $.data.next_cursor — pagination cursor (opaque string; pass it back as cursor for the next page, null when there is no next page)

raw=true (full raw response, camelCase):

  • $.data.query → keyword; $.data.offset — next page offset (e.g. 20)
  • $.data.data[] — result group array; hit items are nested at $.data.data[N].subBoxes[M].items[] (or possibly $.data.data[N].items[]), flattened into items[] by the simplified layer
  • $.data.continueFlag → continue_flag
  • $.data.next_cursor — same as raw=false: opaque pagination cursor (injected at top level). Older versions exposed searchID and other search context in plaintext; upstream no longer returns it
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