Back to WeChat
TikHub·WeChat
WeChat Search V2: WeChat Universal Search
/api/v1/wechat_search/v2/fetch_searchsync$0.015 / callWeChat "Search" (搜一搜) universal search; the vertical is switched by the businesstype string key — just pass a keyword.. Verified to return data: all / official accounts (incl. service accounts and Channels) / articles / Channels videos / stickers.. ⚠️ The other verticals (live streams, Moments, news, books, listen, images, encyclopedia, WeChat Index, underline, comments, photos, mini games, AI sea… (TikHub · WeChat Search V2)
Input
| Field | Type | Required | Description |
|---|---|---|---|
| keyword | string | yes | Search keyword (1-100 chars) |
| business_type | string (all, account, article, video, sticker, underline, encyclopedia, live_stream, …) | — | encyclopedia / livestream / comment / listen / news / photos / book / moments / image / minigame / weixinindex / Vertical key (18 total). Verified to return data: all / account / article / video / sticker. The rest (underline / encyclopedia / livestream / comment / listen / news / photos / book / moments / image / minigame / weixinindex / aisearch) are gated server-side per account & region and currently always come back empty (count=0 plus a nomore message — still billed as a normal call). Use the categories field of an all search for the authoritative per-account tab list. Values outside this list are rejected (422) (default "all") |
| sort | integer | string | — | 0 / 1 / Sort (result page 'sort' dropdown, common to all verticals): default / 0 (relevance) / latest / 1 (newest) / hot / 2 (most liked); string key or integer (default "default") |
| publish_time | integer | string | — | 0 / 1 / 2 / Publish time (result page 'time' dropdown, common): all / 0 / day / 1 / week / 2 / halfyear / 3; string key or integer (default "all") |
| offset | integer | — | Pass 0 for the first page; use cursor to paginate (offset alone does not work — it returns the first page every time) (default 0) |
| cursor | string | — | Pagination cursor: leave empty for the first page; for the next page pass back the cursor returned in the previous response |
| raw | boolean | — | True=raw search response; False=simplified parsed structure (default true) |
Run it
curl -s https://sooma.dev/v1/run \
-H "Authorization: Bearer $SOOMA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"tikhub","endpoint":"/api/v1/wechat_search/v2/fetch_search","input":{}}'
Or ask your agent: it will call inspect for this schema and run it over MCP.