# WeChat Account Profile Scraper — 公众号资料+认证+原创数 (`opspilot.cc/wechat-account-profile-scraper`) Actor

EN — Fetch a WeChat Official Account profile: nickName, IP region, original article count, service type, ban status, linked Channels account. ZH — 公众号资料抓取:昵称/IP 属地/原创文章数/服务类型/封禁状态/关联视频号。

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

## Pricing

$0.06 / 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 Account Profile Scraper — 公众号资料+认证+原创数

> Pass a WeChat Official Account username, get the public profile: nickName, IP region, original article count, service type, ban status, and the linked Channels (视频号) account. One endpoint, three SIÁN ops in one row.

### Why Use This Actor

| Problem | How This Actor Solves It |
|---|---|
| You need to vet a KOL / partner / competitor account before working with them | Returns IP region, original article count, service type, ban status in one call |
| The official WeChat profile page scatters identity / IP / linked-accounts across multiple requests | One row bundles identity, region, original-count, and the linked-Channels `finder_username` |
| You want the data in a clean shape with stable field names | Service-type codes are mapped to friendly labels (`subscription` / `service` / `service_authenticated`); ban status maps to `normal` / `banned` |

### What You Get

For each account username you push one row containing:

- **Identity**: `userName` (`gh_…`), `nickName`, `userRole`, `userRoleLabel`
- **Service / verification**: `serviceType` (int), `serviceTypeLabel` (`subscription` / `service` / `service_authenticated`)
- **Status**: `banType` (int), `banLabel` (`normal` / `banned`)
- **Region**: `ipRegion` (e.g. `新加坡`)
- **Original content signal**: `originalArticleCount` (int), `originalArticleCountLabel` (display string)
- **Cross-platform bridge**: `linkedFinder` (object with `nickname` + `username`) when the WeChat account is bound to a Channels (视频号) account
- **Upstream caveat**: `headUrl`, `signature`, and `unavailable[]` (these fields are always null through this endpoint — use the Article Detail Scraper if you need a head image)
- **Provenance**: `collectedAt`
- **Optional**: `rawData` (full upstream payload when `raw=true`)

Plus a run summary (`SUMMARY` KV store record) with `username`, `nickName`, `serviceTypeLabel`, `ipRegion`, `originalArticleCount`, `linkedFinderUsername`, `tier`, `freeTierRunsToday`.

### Quick Start

#### 1. Run with Example Input

```json
{
  "username": "gh_114e76fd6e5d"
}
```

Click **Start**. Free users get 5 runs/day; paid users are billed once per run on three events (`account-basic-info-result`, `account-original-count-result`, `account-principal-info-result`) to mirror SIÁN's per-event pricing.

#### 2. Export Your Results

Open the **Dataset** tab → CSV / JSON / Excel export.

### Input Reference

#### Top-Level Structure

```json
{
  "username": "gh_114e76fd6e5d",
  "raw": "false"
}
```

#### `username` — Account username

- **Required**: yes
- **Type**: string
- **Pattern**: `^[A-Za-z0-9_\-@.]{3,64}$`
- **Description**: WeChat account username. Three forms supported per upstream docs:
  - `gh_<hex>` (e.g. `gh_114e76fd6e5d`, `gh_363b924965e9`)
  - `gh_<hex>@app` (linked mini-program account, e.g. `gh_363b924965e9@app`)
  - Custom micro-signal ID (e.g. `nikejdi`, `rmrbwx`)
- **Exactly 1 per run** (one upstream call = $0.01).

#### `raw` — Include raw upstream payload

- **Required**: no (default `false`)
- **Type**: enum `false` / `true`
- **Description**: When `true`, the upstream data object is attached as `rawData` on the pushed item. The Actor always requests the simplified shape (`raw=false`) upstream; the `raw` input flag only controls whether the result is preserved.

### Output Reference

#### Account record (one per pushed item)

| Field | Type | Description |
|---|---|---|
| `userName` | string | `gh_…` ID (3 forms supported) |
| `nickName` | string | null | Account display name |
| `userRole` | int | null | Upstream user-role code |
| `userRoleLabel` | string | null | `ordinary` / `other` / null |
| `serviceType` | int | null | Upstream service-type code (0/1/2) |
| `serviceTypeLabel` | string | null | `subscription` / `service` / `service_authenticated` |
| `banType` | int | null | Upstream ban code (0 = normal) |
| `banLabel` | string | null | `normal` / `banned` |
| `ipRegion` | string | null | e.g. `新加坡`, `北京 海淀` |
| `originalArticleCount` | int | null | Number of original articles the account has published |
| `originalArticleCountLabel` | string | null | Display string from upstream (e.g. `4055 original articles`) |
| `linkedFinder` | object | null | `{ nickname, username }` when the account is bound to a Channels (视频号) account. `username` ends in `@finder`. Feed to the Channels V2 endpoints. |
| `headUrl` | null | Always `null` through this endpoint (per upstream docs) |
| `signature` | null | Always `null` through this endpoint (per upstream docs) |
| `unavailable` | string\[] | `["signature", "head_url"]` (always these two) |
| `rawData` | object | undefined | Full upstream payload (only when `raw=true`) |
| `collectedAt` | string | ISO 8601 timestamp |

#### Run summary (`SUMMARY` KV record)

| Field | Description |
|---|---|
| `username`, `nickName` | Input echo + display name |
| `userRole`, `serviceType`, `serviceTypeLabel`, `banType` | Identity codes + friendly labels |
| `ipRegion` | e.g. `新加坡` |
| `originalArticleCount` | Number of original articles |
| `linkedFinderUsername` | Channels (视频号) finder username, or `undefined` |
| `tier` | `paid` or `free` |
| `freeTierRunsToday` | Free-tier counter (only present when tier=free) |
| `autoFilled` | List of fields defaulted by the runtime (for support diagnostics) |
| `collectedAt` | ISO 8601 timestamp |

### Pricing & Limits

- **Free tier**: 5 runs/day, capped at the Actor's default KV store
- **Paid tier**: $0.01 per run, charged across three events to mirror SIÁN's per-event pricing (`account-basic-info-result` + `account-original-count-result` + `account-principal-info-result`)
- **Hard caps**: 1 username per run (cost-control: one upstream request = one $0.01 charge)
- **Upstream latency**: ~30 s on the upstream side; this Actor uses a 60 s client timeout to avoid billing-without-response

### Use it together with the other WeChat Actors

| Where in the pipeline | Actor | Console | Use it to |
|---:|---|---|---|
| before / step ① | [WeChat Article Search Scraper](#) | opspilot.cc/wechat-article-search-scraper | step ① — find account usernames by keyword / business\_type=account |
| before / step ① | [WeChat Universal Search Scraper](#) | opspilot.cc/wechat-universal-search-scraper | step ① — keyword search across 公众号 / 视频号 / 文章 |
| sister Actor / step ② | [WeChat Article Detail Scraper](#) | opspilot.cc/wechat-article-detail-scraper | sister Actor — extract one article's body + identity + comment\_id |
| **You are here** | **WeChat Account Profile Scraper** | opspilot.cc/wechat-account-profile-scraper | step ③ — full account profile (identity, region, original-count, linked Finder) |
| after / step ④ | [WeChat Account Articles Scraper](#) | opspilot.cc/wechat-account-articles-scraper | step ④ — feed `userName` for today's + historical article list with cursor pagination |

**You are here:** **WeChat Account Profile Scraper** (step ③) — run this on its own for `get the public profile of one WeChat Official Account`.

### Support

Open an issue on the [Apify Console run page](https://console.apify.com/actors) for this Actor.

# Changelog

This Actor's version history is a separate document: https://apify.com/opspilot.cc/wechat-account-profile-scraper/changelog.md

# Actor input Schema

## `username` (type: `string`):

WeChat account username. Three forms supported: `gh_<hex>` (e.g. gh\_114e76fd6e5d), `gh_<hex>@app` (linked mini-program account), or a custom micro-signal ID (e.g. nikejdi, rmrbwx). Exactly 1 per run.

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

Add the unprocessed upstream data object as rawData on the pushed item. Default false keeps datasets small; turn on for debugging or downstream pipelines that need the raw response.

## Actor input object example

```json
{
  "username": "gh_114e76fd6e5d",
  "raw": "false"
}
```

# Actor output Schema

## `results` (type: `string`):

Each pushed item contains one parsed account profile.

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

Account identity, IP region, original article count, tier.

# 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-account-profile-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-account-profile-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-account-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,opspilot.cc/wechat-account-profile-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/3JV499ECEjb5un854/builds/Qk4k42kGQNqMhf6iI/openapi.json