Перейти к навигации

How do I continue from a shared Kuaishou post to comments or the creator's work?

With a share link, retrieve the post details with kuaishou.app.fetch_one_video_by_url; with a verified photo_id, reuse the ID directly. Reading comments does not require another search. Save the post ID and the creator’s user ID separately, so a user ID never ends up as a comment target.

For example, a teammate shares a home-cooking technique and wants to know what viewers ask about the preparation. Confirm the post content and the author first, then read the post’s comments. Read the author’s other posts only when you want to compare other methods.

What information do you already have?

MaterialNext step
Post URL or copied share textshare_text for App share details
Verified photo_idPost detail or comments; retain original numeric or short-string eID
Creator’s numeric user IDProfile or account posts
User profile eidProfile lookup; account posts require a confirmed numeric user ID
Display name or account handleA locating clue, rather than a universal user or post identifier

A short-link suffix is not the post ID. Save the original source, the input and the confirmed post, so later observations of the same post link to one stable ID.

Retrieve a shared post

Use kuaishou.app.fetch_one_video_by_url:

{
"action": "kuaishou.app.fetch_one_video_by_url",
"params": {"share_text": "<original_share_text_or_url>"}
}

Send the request to POST https://api.beatapi.io/v1/social-data/call with BeatAPI Bearer authentication. The similarly named Web action takes url instead of share_text and has a separate input contract.

Compare the returned content and creator with the shared post before you record the identifiers. The output contract does not fix the post and author paths in the details response, so find the post and the author in the actual response; do not assume another service’s id or author.id, and do not take the first item by default.

Read the shared post’s comments

Pass the verified photo_id to kuaishou.app.fetch_video_comment and start with an empty pcursor. If you already saved the photo_id, start with the comments.

One share can lead to three different reads. Use the photo_id for comments, the photo_id and parent comment ID for replies, and the creator’s numeric user ID for the creator’s post list. For example, if a viewer asked about pan size, keep the post ID and find the ID of the viewer’s comment. See comments and continuation.

Read the creator’s other work

kuaishou.app.fetch_one_user_v2 accepts a user eid or a numeric userId as user_id; kuaishou.app.fetch_user_post_v2 accepts only the numeric user ID. Read the numeric user ID from the returned profile before you request the post list; do not pass the profile eid.

The account post list supports latest and hot. Recent methods and popular examples answer different questions. Save the sort condition and the query time, then select the posts about preparation.

Reuse a list of verified posts

kuaishou.app.fetch_videos_batch takes comma-separated photo_ids, up to 40 per request, and accepts both numeric and eID post identifiers. Deduplicate the IDs first and keep the input list. Match each returned post by ID; the response order does not necessarily follow the input order.

Put only post IDs in photo_ids, never user IDs. kuaishou.app.fetch_videos_batch returns details only and does not read comments; request comments separately for the posts your research question needs.

For the assistant:

Confirm the post and creator behind this cooking share, preserving source and separate identifiers. Reuse the post ID and prioritize preparation questions in comments. If comparing the author’s other methods, establish their numeric user ID first and attach sources to findings.

Request only the details, comments and account content the research needs, and estimate the cost with current pricing. Analyze saved originals without requesting again.