How do I verify a brand roster of WeChat Official Accounts and linked Channels?
To find the Channel linked to a WeChat Official Account, request the profile with wechat_mp.v2.fetch_account_profile and the account’s verified username, then read data.finder_username. To identify the company behind the account, record the operator shown on the account’s public profile and check the registration separately. For a partnership shortlist, compare observed publishing frequency and headline reads. Ask the account owner for follower figures.
Fetch the profile using the Official Account ID
If you already have article details, take data.content.user_name from the article-detail response. With only a display name, start with a public article from the intended account and verify the account ID. Pass the verified ID as username in the profile request below, and keep the returned display name for reference.
Turn the response into an account roster
Check that data.user_name identifies the Official Account you intended to look up. If you queried a custom WeChat ID and the response returns a canonical account ID, keep the custom ID and the canonical ID in separate columns.
For example, when the profile returns a linked Channel ID, track the brand’s articles through the Official Account and the brand’s videos through the linked Channel. If a report names a company as the operator, attach the account’s public operator information and the matching registration record. The profile route lists the biography (signature) and the avatar (head_url) as unavailable. If a saved article response contains an avatar, keep the avatar with the article response as the source.
What can I actually retrieve?
Pass an explicit raw:false. The provider’s profile description documents these fields under data:
A missing follower field does not mean zero followers. Do not estimate exact followers by dividing article reads by a chosen ratio. A service-type code or a nickname is not evidence of corporate ownership either.
Build an account-to-Channel evidence table from saved profiles
For ten specified Official Accounts, the immediate deliverable is an account-to-Channel link table; weekly monitoring is a separate setup. Request each profile with an explicit raw:false. link_accounts.py below runs offline on 1–10 saved successful profile responses. The script records a missing, null, empty or unavailable link as a separate state, and prepares a first-page video request only when finder_username fits the published Channels username contract. The script never searches for a matching display name and makes no network call.
Save profile-pages.json beside the responses:
Save the script below as link_accounts.py and run python3 link_accounts.py profile-pages.json account-link-review. Paths in profile-pages.json are relative to the manifest, and the output directory must not exist yet. Resolve failed or mismatched profiles before running the batch instead of silently dropping them. A custom alias and the returned canonical ID stay in separate columns. A gh_ identity, including an @app suffix, must match exactly; do not strip the suffix to get past a mismatch.
account-links.csv is the local deliverable. Each row points through evidence.json to an archived raw profile and the profile’s request and collection time. Each unexecuted-videos-*.json file is an optional next request, not a fetched video record. The first video page uses last_buffer="" and its own video-list budget; further pages need the returned cursor and an approved scope. A missing or unsupported finder identifier triggers no paid name search and no guessed conversion.
Ten new accounts take ten profile requests. Count the pages fetched from linked Channels separately. See BeatAPI pricing.
To watch both the Official Accounts and the linked Channels weekly, you also need separate article and video collection state, a scheduler and a tested destination. link_accounts.py installs none of those, fetches no media, does not combine the two timelines and sends no notifications. The hashes in evidence.json show that the archived bytes are unchanged; the hashes do not prove that the content is true or verify where the response came from. Keep the original evidence local and share a reviewed copy.
For one organization’s weekly brief, keep separate sections for Official Account articles and Channels videos. Record the link evidence at the top, then keep the Official Account username, the Channels finder username and the collection date with each section. If one route fails, report the material from the other route and keep the failed read on the follow-up list.
Verify the operator separately
Open the public profile of the verified Official Account. If the profile lists an operator or verification details, record the displayed wording, the account source and the date checked. To verify a mainland Chinese company registration, search the exact legal name or the credit code in the National Enterprise Credit Information Publicity System. Match the registration record to the operator that the account displays. Hold ambiguous or conflicting records for review. Keep the company’s incorporation date, the platform verification date and the account registration date in separate fields.
Compare headline reads and publishing frequency for a shortlist
Use the article list to cover a window such as the last 28 days, and deduplicate by account and publication batch. To compare headline articles, verify that idx=1 identifies the first article of each returned batch, and count each headline once. Use standard engagement stats for read snapshots. Apply the same window and sampling rule to every account.
Record findings such as “28 days checked, 8 publication batches found, headline reads available for 5 of 8.” From the 28-day record, report about two observed batches per week and the average of the five valid headline read counts, with the sample size and the snapshot date. Keep measured zeros, and list missing counts separately. If the scan did not finish, report “at least eight batches.” Leave follower and active-follower counts blank unless the account owner supplies a separate dated report that defines the counts.

