> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do I verify a brand roster of WeChat Official Accounts and linked Channels?

> Verify provided account identities, interpret linked-Channel states and export sourced plans without claiming ownership, followers or installed monitoring.

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](/faq/wechat-account-identifier). Pass the verified ID as `username` in the profile request below, and keep the returned display name for reference.

```bash
curl --max-time 30 -sS https://api.beatapi.io/v1/social-data/call \
  -H "Authorization: Bearer $BEATAPI_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"action":"wechat_mp.v2.fetch_account_profile","params":{"username":"<username>","raw":false}}' \
  -o wechat-account-profile.json -w '%{http_code}\n'
```

## 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.

| What you see                                                         | What to record and do next                                                                                                                                             |
| -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A usable `finder_username`                                           | Keep the Official Account ID, Channel ID, request ID and collection time. To fetch posts, use the [Channels video inventory](/guides/wechat-channels-video-inventory). |
| A Channel with the same display name or no linked ID in the response | Keep the source and mark the account-to-Channel relationship for review.                                                                                               |
| A request for company ownership or partner reach                     | Follow the operator check and the headline sampling steps below, and keep the sources for each step.                                                                   |

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`:

| Field                                            | Use in an account review                                                      |
| ------------------------------------------------ | ----------------------------------------------------------------------------- |
| `user_name`, `nick_name`                         | Stable account identifier and displayed name, kept separate                   |
| `user_role`, `service_type`                      | Raw role/service codes, not an invented legal-company name                    |
| `ban_type`                                       | Account status code; the description defines 0 as normal                      |
| `ip_wording`                                     | Platform-displayed IP region, not registered company address                  |
| `original_article_count`, `original_content_str` | Original-content information, not followers or total historical completeness  |
| `finder_username`, `finder_nickname`             | Explicit linked Channels identifier and displayed name                        |
| `unavailable`                                    | Fields the profile route cannot provide, kept distinct from a legitimate zero |

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:

```json
[{"action":"wechat_mp.v2.fetch_account_profile","params":{"username":"gh_example","raw":false},"http_status":200,"collected_at":"2026-11-17T09:00:00Z","response_file":"profile-1.json"}]
```

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.

```python
import csv,hashlib,json,pathlib,re,sys
from datetime import datetime
manifest,out=map(pathlib.Path,sys.argv[1:3]);manifest_bytes=manifest.read_bytes();entries=json.loads(manifest_bytes)
if not isinstance(entries,list) or not 1<=len(entries)<=10:raise ValueError('Select 1–10 recorded profile requests')
ACTION='wechat_mp.v2.fetch_account_profile'
rows,sources,seen,requests=[],[],set(),set()
def valid_id(value):return isinstance(value,str) and len(value)<=80 and re.fullmatch(r'[0-9A-Za-z][-_0-9A-Za-z]{1,63}(@[0-9A-Za-z]{1,16})?',value)
def safe(value):
 if value is None:return ''
 value=str(value)
 return "'"+value if value.startswith(('=','+','-','@','\t','\r','\n')) else value
for i,e in enumerate(entries,1):
 params=e.get('params');requested=params.get('username') if isinstance(params,dict) else None
 if e.get('action')!=ACTION or not isinstance(params,dict) or set(params)!={'username','raw'} or params['raw'] is not False or not valid_id(requested):raise ValueError('Use explicit simplified profile and valid username')
 if type(e.get('http_status')) is not int or e['http_status']!=200:raise ValueError('Resolve failed profiles separately; do not silently omit an account')
 collected=e.get('collected_at')
 if not isinstance(collected,str) or datetime.fromisoformat(collected.replace('Z','+00:00')).tzinfo is None:raise ValueError('Record collection time with timezone')
 raw=(manifest.parent/e['response_file']).read_bytes();body=json.loads(raw);data=body.get('data')
 if body.get('action')!=ACTION or body.get('status')!='succeeded' or body.get('error') is not None or not isinstance(data,dict):raise ValueError('Invalid successful profile envelope')
 rid=body.get('request_id')
 if not isinstance(rid,str) or not rid.strip() or rid in requests:raise ValueError('Missing or duplicate request ID')
 requests.add(rid);returned=data.get('user_name')
 if not valid_id(returned):raise ValueError('Missing returned account identity')
 if requested.startswith('gh_') and returned!=requested:raise ValueError('Canonical identity mismatch; do not normalize @app')
 if returned in seen:raise ValueError('Repeated canonical account; select one observation')
 seen.add(returned)
 unavailable=data.get('unavailable',[])
 if not isinstance(unavailable,list) or any(not isinstance(x,str) for x in unavailable):raise ValueError('Invalid unavailable flags')
 finder=data.get('finder_username');name=data.get('finder_nickname')
 if name is not None and not isinstance(name,str):raise ValueError('Invalid linked display name')
 if 'finder_username' in unavailable:state='unavailable' if finder in (None,'') else 'inconsistent_unavailable'
 elif 'finder_username' not in data:state='missing'
 elif finder is None:state='null'
 elif finder=='':state='empty'
 elif isinstance(finder,str) and 10<=len(finder)<=256 and re.fullmatch(r'v2_[0-9a-fA-F]+@finder',finder):state='linked_identifier_returned'
 else:state='unsupported_identifier'
 next_request={'action':'wechat_channels.v2.fetch_user_videos','params':{'username':finder,'raw':False,'last_buffer':''}} if state=='linked_identifier_returned' else None
 row={'requested_username':requested,'returned_username':returned,'identity_relation':'exact' if requested==returned else 'alias_returned_by_profile','profile_request_id':rid,'collected_at':collected,'finder_username_raw':json.dumps(finder,ensure_ascii=False),'finder_nickname_raw':json.dumps(name,ensure_ascii=False),'link_state':state,'legal_common_owner_verified':'false','source_index':i}
 rows.append(row);sources.append({'row':row,'raw':raw,'next':next_request})
out.mkdir(exist_ok=False)
with (out/'account-links.csv').open('x',encoding='utf-8-sig',newline='') as f:
 w=csv.DictWriter(f,fieldnames=list(rows[0]));w.writeheader();w.writerows({k:safe(v) for k,v in r.items()} for r in rows)
evidence=[]
for i,source in enumerate(sources,1):
 name='profile-%02d.json'%i;(out/name).write_bytes(source['raw'])
 evidence.append({'source_index':i,'filename':name,'sha256':hashlib.sha256(source['raw']).hexdigest(),'request':entries[i-1],'link_state':source['row']['link_state']})
 if source['next'] is not None:(out/('unexecuted-videos-%02d.json'%i)).write_text(json.dumps(source['next'],ensure_ascii=False,indent=2),encoding='utf-8')
(out/'manifest.json').write_bytes(manifest_bytes)
(out/'evidence.json').write_text(json.dumps({'sources':evidence,'manifest_sha256':hashlib.sha256(manifest_bytes).hexdigest(),'executed_calls':0,'weekly_monitoring_installed':False,'identity_basis':'recorded profile response; not corporate ownership or independent live verification'},ensure_ascii=False,indent=2),encoding='utf-8')
print(json.dumps({'accounts':len(rows),'linked_identifiers':sum(r['link_state']=='linked_identifier_returned' for r in rows),'executed_calls':0}))
```

`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](https://beatapi.io/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](https://www.gsxt.gov.cn/). 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](/guides/wechat-incremental-articles) 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](/faq/wechat-article-metrics) 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.