WeChat Channels Video Detail Scraper

EN — Pull full WeChat Channels (视频号) video detail by ID. Get media URL + decode_key (downloadable), metrics (read/like/fav/forward/comment), author, location, timestamps.

ZH — 通过 ID 抓取视频号作品详情：媒体地址 + decode_key（可下载）、互动数据、作者、IP 属地、发布时间戳。

What you get

For one video ID you get back:

• Media download — media.url + media.url_token + media.full_url + media.decode_key (the decode_key is what you need to actually decrypt and download the video; media.url alone returns encrypted bytes)
• Metrics — read_count / like_count / fav_count / forward_count / comment_count
• Identity — username (finder, v2_...@finder), nickname, id (string), objectNonceId (string)
• Content — title / description / shortTitle / coverImgUrl / objectType / createTime (unix seconds)
• Location — city / country / longitude / latitude / poiName (when posted from a tagged location)
• Provenance — sourceEndpoint (fetch_video_detail), fetchedAt (ISO 8601)

Use it together with the other WeChat Actors

Where in the pipeline	Actor	Console	Use it to
before / step ①	WeChat Channels Video Search Scraper	opspilot.cc/wechat-channels-video-search-scraper	step ① — find video URLs by keyword, get exportId
before / step ①	WeChat Universal Search Scraper	opspilot.cc/wechat-universal-search-scraper	step ① — same as above, cross-vertical
You are here	WeChat Channels Video Detail Scraper	opspilot.cc/wechat-channels-video-detail-scraper	step ② — turn exportId into full media + metrics
after / step ③	WeChat Channels Video Comments Scraper	opspilot.cc/wechat-channels-video-comments-scraper	step ③ — feed object_id to harvest the comment thread
after / step ③	WeChat Channels User Videos Scraper	opspilot.cc/wechat-channels-user-videos-scraper	step ③ — feed username to harvest the creator's full catalog
after / step ③	WeChat Channels User Profile Scraper	opspilot.cc/wechat-channels-user-profile-scraper	step ③ — feed username for follower / like / works stats

Input

The Actor accepts four mutually-exclusive IDs, in priority order:

1. object_id (preferred) — numeric objectId from a previous fetch_user_videos / fetch_video_comments call
2. export_id (fallback) — the export/... token from fetch_search_videos results (expires quickly, prefer object_id)
3. object_nonce_id (auxiliary) — improves hit rate when paired with object_id; required when object_id is missing
4. share_url (last resort) — WeChat Channels short link (https://weixin.qq.com/sph/...)

If all four are empty, the Actor fails fast with At least one of object_id / export_id / object_nonce_id / share_url is required. — no upstream charge.

Pricing & Limits

• Free tier: 5 runs/day, capped at the Actor's default KV store
• Paid tier: $0.01 per video-detail-result event
• Hard caps: 1 ID per run (one upstream call = one $0.01 charge; pagination is handled by passing the next object_id)
• 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
• export_id expires within minutes — capture object_id from the search response if you want to re-fetch later
• Posted location is null when the creator did not tag a POI

Support

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