WeChat Account Profile Scraper — 公众号资料+认证+原创数

✨ What you get

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.

💼 Use cases

• Vetting a KOL, partner or competitor account in one call — ipRegion, originalArticleCount, serviceTypeLabel and banLabel come back on a single row, which is exactly the set of facts you want before opening a conversation.
• Checking account type and verification instead of decoding codes — the service-type integer is mapped to subscription / service / service_authenticated, so you do not have to know the platform's code table.
• Finding the Channels (视频号) side of a 公众号 account — when the account is bound to a Channels identity, linkedFinder.username ends in @finder and drops into the Channels Actors as the next step.
• Populating a due-diligence sheet — identity, region, original-content count and ban status in one exportable row is enough to qualify or disqualify a batch of accounts before you spend deeper calls on them.

✅ Who this is for

• Business-development and partnership teams — qualifying WeChat accounts before signing, who care about region, verification type and ban status more than content.
• Cross-border and overseas teams — checking the ipRegion of an account they cannot visit, including accounts registered outside mainland China.
• Creator-economy researchers — who need the original-article count as a proxy for whether an account publishes original work or only reposts.
• Pipelines that start from identity — anything that needs the canonical gh_… username once, up front, so every later call in the chain is aimed at the right account.

❌ Who this is NOT for

• You need the avatar or the account signature — headUrl and signature are always null through this endpoint and unavailable always lists those two names. For a head image, read it off an article via the detail Actor.
• You need follower, reading or view counts — this profile has no audience numbers at all. Reach metrics live on the Channels profile Actor, and per-article read counts on the metrics Actor.
• You want to batch profiles — the hard cap is exactly one username per run, so a hundred accounts means a hundred runs, each of which pays its own latency.
• You are originalArticleCount as total output — it counts original articles only. Reposted, curated and non-original posts are not in that number, so it is an originality signal, not a volume or ranking metric.
• You assume a run always produces a row — the platform can take around thirty seconds to answer and this Actor uses a sixty-second client timeout to avoid billing without a response, so a run can end with no profile rather than a broken one.

🚀 Quick start

1. Run with Example Input

{
  "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 parameters

Top-Level Structure

{
  "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 Data provider 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 profile per run).

raw — Include raw Data provider payload

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

📤 Output

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	Data provider user-role code
userRoleLabel	string | null	ordinary / other / null
serviceType	int | null	Data provider service-type code (0/1/2)
serviceTypeLabel	string | null	subscription / service / service_authenticated
banType	int | null	Data provider 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 Data provider (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 Data provider docs)
signature	null	Always null through this endpoint (per Data provider docs)
unavailable	string[]	["signature", "head_url"] (always these two)
rawData	object | undefined	Full Data provider 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

💰 Billing

• Free tier: 5 runs/day, capped at the Actor's default KV store
• Paid tier: pay-per-result, charged on the profile rows returned
• Hard caps: 1 username per run
• Data latency: the provider can take ~30 s to respond; this Actor uses a 60 s client timeout to avoid billing-without-response

📚 Resources

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

📜 Notes & caveats

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

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.