# WeChat Channels Video Detail Scraper (`opspilot.cc/wechat-channels-video-detail-scraper`) Actor

EN — Pull full WeChat Channels (视频号) video detail by object\_id / export\_id / share\_url: media URL + decode\_key (downloadable), metrics (read/like/fav/forward/comment), author, location, timestamps. ZH — 通过 object\_id / export\_id / share\_url 任一抓取视频号作品详情：媒体地址 + decode\_key（可下载）、互动数据、作者、IP 属地、发布时间戳。

- **URL**: https://apify.com/opspilot.cc/wechat-channels-video-detail-scraper.md
- **Developed by:** [wang wei](https://apify.com/opspilot.cc) (community)
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.10 / actor start

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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](https://console.apify.com/actors/VAtqWhR0gxKlezuPU) | opspilot.cc/wechat-channels-video-search-scraper | step ① — find video URLs by keyword, get `exportId` |
| before / step ① | [WeChat Universal Search Scraper](https://console.apify.com/actors/0Gl2Wi2L7vo9GLF1T) | 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](https://console.apify.com/actors/YtFcmpVepdn5hBP9q) | opspilot.cc/wechat-channels-video-comments-scraper | step ③ — feed `object_id` to harvest the comment thread |
| after / step ③ | [WeChat Channels User Videos Scraper](https://console.apify.com/actors/rzHbAt3tTT5pbrG5q) | opspilot.cc/wechat-channels-user-videos-scraper | step ③ — feed `username` to harvest the creator's full catalog |
| after / step ③ | [WeChat Channels User Profile Scraper](https://console.apify.com/actors/YTWhw209Ic7PxM8d0) | 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](https://console.apify.com/actors) for this Actor.

# Actor input Schema

## `object_id` (type: `string`):

Numeric objectId of the WeChat Channels video. Highest priority among the four ID options. Source: upstream `fetch_video_comments` / `fetch_user_videos` responses.

## `export_id` (type: `string`):

Video exportId starting with `export/`. Expires quickly — use `object_id` when available. Source: upstream `fetch_search_videos` / `fetch_search` results.

## `object_nonce_id` (type: `string`):

Numeric objectNonceId. Improves hit rate when paired with `object_id`; required when `object_id` is missing.

## `share_url` (type: `string`):

WeChat Channels short share link (`https://weixin.qq.com/sph/...`). Only used when `object_id`, `export_id`, and `object_nonce_id` are all empty.

## `raw` (type: `string`):

Attach the unprocessed upstream data object as `raw`. `false` returns only the flattened schema.

## Actor input object example

```json
{
  "object_id": "15006730713638308387",
  "raw": "false"
}
```

# Actor output Schema

## `dataset` (type: `string`):

Normalized WeChat Channels video record — id, objectNonceId, username, nickname, title, description, shortTitle, createTime, objectType, coverImgUrl, location, readCount, likeCount, favCount, forwardCount, commentCount, media (url + decode\_key), sourceEndpoint, and the original upstream payload in raw.

## `summary` (type: `string`):

object\_id / username, source kind (object\_id vs share\_url vs username), upstream request count, request cost, and any error details.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("opspilot.cc/wechat-channels-video-detail-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("opspilot.cc/wechat-channels-video-detail-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call opspilot.cc/wechat-channels-video-detail-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,opspilot.cc/wechat-channels-video-detail-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7qMMl0n4LMJaCsx0F/builds/HmopacGCEU4Ufarc1/openapi.json