Search Videos Within a WeChat Channel

Search Videos Within a WeChat Channel

POST https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_search_channel_videos

Search Videos Within a WeChat Channel

cURL

curl --request POST \
  --url https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_search_channel_videos \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "username": "v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder",
  "keyword": "news",
  "cursor": "<string>",
  "raw": true
}
'

200

{
  "code": 200,
  "request_id": "<string>",
  "message": "Request successful. This request will incur a charge.",
  "message_zh": "请求成功，本次请求将被计费。",
  "support": "Discord: https://discord.gg/aMEAS8Xsvz",
  "time": "<string>",
  "time_stamp": 123,
  "time_zone": "America/Los_Angeles",
  "docs": "<string>",
  "cache_message": "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_zh": "本次响应已缓存，可通过下方 URL 直接查看，有效期 24 小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。",
  "cache_url": "<string>",
  "router": "",
  "params": {},
  "data": "<unknown>"
}

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

curl -X POST "https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_search_channel_videos" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'  # see request schema below

Authorizations

Authorization · string · header · required

AIsa API key. Get yours at https://aisa.one

Body

application/json

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"

keyword · string · required

Keyword to search within this channel (1-100 chars

Required string length: 1 - 100

Example:

"news"

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

200 - application/json

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

code · integer · default: 200

HTTP status code

request_id · string | null

Unique request identifier

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

Response message (EN-US)

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

Response message (ZH-CN)

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

docs · string | null

Link to the API Swagger documentation for this endpoint

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

router · string · default: ""

The endpoint that generated this response

params · any · default: {}

The parameters used in the request

data · any | null

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.