Skip to main content
POST
Get WeChat Channels User Profile & Stats
Get WeChat Channels User Profile & Stats 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

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). Source: the username field of video objects in fetch_video_detail / fetch_user_videos responses; or convert a sph… short ID via fetch_channel_id_to_username. E.g. v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder (People's Daily).

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_user_videos = POST /tikhub/wechat_channels/v2/fetch_user_videos (operationId: post_tikhub_wechat_channels_v2_fetch_user_videos); 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$
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

  • Account homepage profile and interaction stats

Response structure & JSON Path

raw=false (simplified, flattened snake_case):

  • $.data.username — finder username
  • $.data.nickname / $.data.signature / $.data.head_url (avatar) / $.data.region (IP region)
  • $.data.fans_count — follower count. Note: some accounts (e.g. People's Daily) return 0
  • $.data.feeds_count — video count (e.g. 10555)
  • $.data.like_count / $.data.fav_count / $.data.forward_count — like / favorite / forward counts (0 for some accounts)
  • $.data.friend_follow_count — friend-follow count
  • $.data.live_duration_hours — accumulated live streaming hours
  • $.data.original_flag — original-content flag
  • $.data.collection_count — collection count (e.g. 6; details via fetch_user_collections)
  • $.data.verify_desc — verification description (may be null)
  • $.data.linked_accounts[] — linked official accounts [{nickname, type}]

raw=true (full raw response, nested camelCase):

  • $.data.contact.nickname / .signature / .headUrl → nickname / signature / head_url
  • $.data.contact.username → username; $.data.contact.originalFlag → original_flag
  • $.data.contact.authInfo (authProfession / authIconType …) — verification info
  • $.data.ipRegionInfo.regionText → region
  • $.data.fansCount → fans_count (also 0 for some accounts); $.data.feedsCount → feeds_count
  • $.data.feedsLikeCount / .feedsFavCount / .feedsForwardCount → like_count / fav_count / forward_count
  • $.data.liveDurationHours → live_duration_hours; $.data.collectionListInfo.collectionCount → collection_count
  • $.data.bizInfo.info[] (bizNickname / serviceTypeName) → linked_accounts[]
  • Also contains dozens of raw fields like $.data.object[] (first-screen video list), $.data.anchorStatInfo (live session stats), $.data.lastBuffer / $.data.continueFlag (pagination of the first-screen videos; generally unused here since this endpoint is for profile data).

API references: fetch_user_collections = POST /tikhub/wechat_channels/v2/fetch_user_collections (operationId: post_tikhub_wechat_channels_v2_fetch_user_collections).

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.