WeChat Channels User Videos Scraper

EN — Scrape all videos uploaded by a WeChat Channels (视频号) creator. Get one or many pages of video metadata with author, media URL, decode_key, like / comment / share counts, plus a next_buffer for chaining.

ZH — 通过视频号 finder username 抓取创作者的全部作品：视频元数据 + 媒体地址 + 互动数据，支持 last_buffer 翻页。

What you get

For one creator username you get back one record per video (across as many pages as max_pages allows):

• Identity — id (string), objectNonceId (string), username, nickname
• Content — title / description / shortTitle / coverImgUrl / objectType / createTime (unix seconds)
• Location — city / country / poiName (when posted from a tagged location)
• Media download — media.url + media.url_token + media.full_url + media.decode_key (decrypt and combine to actually download)
• Metrics — read_count / like_count / fav_count / forward_count / comment_count
• Provenance — sourceEndpoint, fetchedAt

The Actor also writes a SUMMARY record to its KV store with nextBuffer / pagesFetched / totalPushed so the next page can be pulled without re-running the search.

Use it together with the other WeChat Actors

Where in the pipeline	Actor	Console	Use it to
before / step ①	WeChat Channels User Profile Scraper	opspilot.cc/wechat-channels-user-profile-scraper	step ① — find a creator's username from a nickname or signature
before / step ①	WeChat Channels Video Search Scraper	opspilot.cc/wechat-channels-video-search-scraper	step ① — find creator usernames from a keyword
You are here	WeChat Channels User Videos Scraper	opspilot.cc/wechat-channels-user-videos-scraper	step ② — turn a username into a catalog of object_ids
after / step ③	WeChat Channels Video Detail Scraper	opspilot.cc/wechat-channels-video-detail-scraper	step ③ — enrich each object_id with the full detail payload
after / step ③	WeChat Channels Video Comments Scraper	opspilot.cc/wechat-channels-video-comments-scraper	step ③ — feed each object_id to harvest the comment thread

Input

The Actor requires username in v2_<hex>@finder format (10–256 chars). Two optional fields control scope:

• last_buffer (base64 cursor, optional) — pass back the nextBuffer field from a previous run's SUMMARY to continue where you left off.
• max_pages (integer, 1–50, default 1) — cap the run. Each page returns ~15 videos. Use 1 for a quick test, 5+ for a full catalog.
• raw (true/false, default false) — attach the unprocessed upstream payload per video as raw.

If username is missing or malformed the Actor fails fast with username is required (v2_<hex>@finder format). — no upstream charge.

Pricing & Limits

• Free tier: 5 runs/day, capped at the Actor's default KV store
• Paid tier: $0.01 per user-videos-result event (one charge per page fetched)
• Hard caps: 50 pages per run; ~15 videos per page = up to ~750 videos per run
• Upstream latency: ~30 s on the upstream side; this Actor uses a 60 s client timeout to avoid billing-without-response

Caveats

• 64-bit numeric IDs (id, objectNonceId, decodeKey) are returned as strings to preserve precision (JavaScript Number overflows past 2^53)
• media.url returns encrypted bytes; to actually download a playable video you must combine it with media.decode_key
• last_buffer is opaque — pass it back verbatim, do not parse or re-encode
• A creator's full catalog can span 100+ pages; budget accordingly with max_pages
• The first page typically returns up to 15 videos; later pages may have fewer

Support

Open an issue on the Apify Console run page for this Actor.