How do I use a Channels share link, sph ID or export ID to research videos and comments?
Use a v2_…@finder ID to list an account’s videos and a numeric video ID to read comments on one video. If you only have a share link or an export/… identifier from WeChat Search, fetch the video details with data:wechat_channels.v2.fetch_video_detail first, verify the returned title and account, then use the returned numeric video ID for comments. An sph… account short ID needs conversion with data:wechat_channels.v2.fetch_channel_id_to_username before the account list.
Choose the next step from the identifier you have
An export/… value locates a video for the detail request; an export/… value is not a numeric comment-target ID. Keep the export/… string as copied: do not decode the string, and do not assume a fixed validity period.
When WeChat Search gives you only an export/… identifier, request the video detail with the export/… value. Save both the original search identifier and the verified numeric video ID. Request comments with the numeric video ID, and keep the search identifier to trace how you found the post.
Look up comments from a shared video
POST the body below to https://api.beatapi.io/v1/social-data/call with BeatAPI Bearer authentication. Replace the example link with the complete Channels share link you received.
For example, a colleague sends a product-introduction video, and you want to identify the video’s account and investigate viewer questions:
- Retrieve the video details with the share link, and confirm that the returned title and account match the target.
- Save
data.idas the video ID anddata.usernameas the account identifier, together with the collection time and the original response. - Use the video ID for the comment workflow, or the account identifier for the account’s video directory.
Reuse the verified video ID and account identifier for later steps. Do not resolve the same link again just to organize a table.
For an assistant connected to BeatAPI:
Confirm this video’s title and publishing account, then review its available comments for questions about product eligibility. Keep the original wording and discussion context. If research needs the account’s other videos, first show relevant candidates.
Why might a detail request return a different video from the link?
data:wechat_channels.v2.fetch_video_detail applies its inputs in priority order: object_id, then export_id, then share_url. Supply only the one target you intend to inspect. Do not combine an old video ID with a new share link.
Keep account identifiers, video IDs and parent-comment IDs separate. object_nonce_id is an auxiliary detail locator, not a parent comment’s comment_id. To expand a reply thread, use the actual parent-comment identifier from the comments response.
Prepare one unambiguous target locally
channels_identity.py (below) prepares a request for one input type. After you save a real response, channels_identity.py prepares the account-list request or the comment request, keeps the sources and checks the returned identifiers. Creating the request files does not run any retrieval.
The same visible string is not a universal WeChat identifier, so choose one explicit input type:
- A
v2_…@finderaccount goes directly to the account-video list. - An
sph…account short ID needs conversion first. - A numeric video ID, an
export/…search identifier and an HTTPS Channels share link select the video-detail route.
channels_identity.py never treats an account name or account ID as a video ID, and never fills the three competing detail fields at once.
- Save the Python script at the end of this page as
channels_identity.py. - Run the one
preparecommand that matches your input. The commands only write JSON, and the values are placeholders:
- Replace the placeholder with the exact copied value;
channels_identity.pyrejects the placeholders. A real share URL must use theweixin.qq.com/sph/host and path, with no query or fragment. Do not strip extra URL data silently, and do not infer a token from arbitrary sharing text. Treatexport/…identifiers as opaque strings: do not decode anexport/…value, change capitalization, or calculate anobject_idfrom the string. No expiry duration is promised forexport/…identifiers. - Check the selected action in
request.json, then estimate the resolution request plus the chosen list or comment request with current pricing. Skip resolution when a usable identifier is already available, and continue local processing from saved responses. - For an approved conversion or detail request, save the full direct response once in a new directory:
For an sph ID conversion, send conversion-request/request.json instead. Check the HTTP status and the saved response before verification, and do not rerun the request into the same files.
Turn the saved resolution into the correct next request
- Run
python3 channels_identity.py verify detail-request/request.json captured-call/response.json identity-review. For an account conversion, substituteconversion-request/request.json. - Check what
channels_identity.py verifyaccepts:- With
raw:false, the conversion response returnsdata.channel_idanddata.username.channels_identity.pyrequires thechannel_idecho to match the input anddata.usernameto have the published finder format. - The detail response returns
data.idanddata.username.channels_identity.pyaccepts only an original nonzero digit-string ID or a safe positive integer; an unsafe numeric ID cannot be repaired after rounding. For a numeric input, the returned ID must match the requested ID exactly. - For an export or share-link input, compare the returned title and account with the intended video yourself. The local source hash does not prove which video the resolution returned.
- With
- Read the private output folder
identity-review. The folder keeps the exact source bytes and an identity audit, and contains an unexecutedaccount-videos-request.json. A valid video detail also producescomments-request.jsonwith the video’s ID, an empty parent and the first-page cursor.account-videos-request.jsonandcomments-request.jsonare alternative next steps; run only the one your research needs.
channels_identity.py verify stops without output on a conversion with no match, a wrong echo, a failed envelope, an invalid username or an unsafe video ID. A parsed conversion selects the matching account item; the conversion does not prove account ownership, and a similar display name is not enough to choose the next target.
After choosing and collecting either the account-video list or the comment step, export the results with the account-page exporter or the comment exporter. Keep the raw detail response private because the raw detail can contain media URL tokens and decoding keys that identifier handoff does not need. channels_identity.py never downloads or decrypts media. Source hashes check local byte consistency rather than server authenticity. Contract basis: the documented WeChat Channels v2 action input and response schemas.

