Get WeChat Channels User Collections

Get WeChat Channels User Collections

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

Get WeChat Channels User Collections

cURL

curl --request POST \
  --url https://api.aisa.one/apis/v1/tikhub/wechat_channels/v2/fetch_user_collections \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "username": "v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder",
  "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>"
}

Get WeChat Channels User Collections

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_user_collections" \
  -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

WeChat Channels finder username (v2_…@finder format). E.g. v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder (People's Daily).

Required string length: 10 - 256

Pattern: ^v2_[0-9a-fA-F]+@finder$

Example:

"v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder"

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

• Collection list

Response structure & JSON Path

raw=false (simplified, snake_case):

• $.data.username — finder username
• $.data.count — total collections (e.g. 6)
• $.data.collections[] — collection array, per item (N is the index):
  • $.data.collections[N].topic_id — collection ID (numeric, pass to fetch_collection_videos, e.g. 14616794565351966924)
  • $.data.collections[N].name — collection name
  • $.data.collections[N].desc — collection description (may be empty string)
  • $.data.collections[N].cover_url — collection cover
  • $.data.collections[N].feed_count — number of videos in the collection
  • $.data.collections[N].topic_type — collection type (e.g. 16, matches topic_type of fetch_collection_videos)

raw=true (full raw response, camelCase):

• $.data.collectionCount → count
• $.data.collectionInfo[] → collections[], per item:
  • $.data.collectionInfo[N].collectionTopicId → topic_id (number; collectionTopicIdStr provides a string alias)
  • $.data.collectionInfo[N].collectionName → name
  • $.data.collectionInfo[N].collectionDesc → desc
  • $.data.collectionInfo[N].coverImgUrl → cover_url
  • $.data.collectionInfo[N].feedCount → feed_count
  • $.data.collectionInfo[N].collectionTopicType → topic_type
  • Also raw fields like lastUpdateTime / readCount / categoryId
• $.data.lastBuffer — pagination cursor of the collection list (usually empty; few collections, no pagination needed)

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

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.