> 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 select Kuaishou short tutorials and discover viewer questions?

> Narrow cooking-tutorial candidates by period, duration and ordering, then read selected comments for conditions and editorial questions.

To find short Kuaishou tutorials and the questions viewers still ask, search with `kuaishou.app.search_comprehensive` using period, duration and ordering filters, select the posts that actually demonstrate the steps, and read those posts' comments with `kuaishou.app.fetch_video_comment`. The result is a table of viewer questions with excerpts, source posts and the conditions to check, which you can use as sourced editorial reasons for the next tutorial.

The example below researches home-cooking tutorials and selects last-week posts under one minute, ordered by likes. When the tutorial needs a complete process rather than a short explanation, use a longer `duration`.

## 1. Narrow the initial batch

Use `kuaishou.app.search_comprehensive` when you need filters: `kuaishou.app.search_comprehensive` supports ordering, period and duration. `search_video_v2` accepts only a keyword and a cursor.

| Purpose                         | Supported conditions                                       |
| ------------------------------- | ---------------------------------------------------------- |
| Recent approaches               | `publish_time: one_day/one_week/one_month`, or `all`       |
| Higher-interaction references   | `sort_type: most_likes`, or `all` comprehensive / `newest` |
| Short steps or longer processes | `duration: under_1_min/1_to_5_min/over_5_min`, or `all`    |

Choose one condition set for the research round, and save the keyword, the filters and the actual query time.

## 2. Prepare a request with Python

Save the script below as `build_kuaishou_search.py`. `build_kuaishou_search.py` writes a request file that combines your keyword with the fixed filters from step 1. The script runs locally, sends nothing, and refuses to overwrite an existing request file.

```python
import json,pathlib,sys
keyword,output=sys.argv[1:3]
if not keyword.strip():raise ValueError("Keyword is required")
request={"action":"kuaishou.app.search_comprehensive","params":{"keyword":keyword,
 "sort_type":"most_likes","publish_time":"one_week","duration":"under_1_min","pcursor":""}}
with pathlib.Path(output).open("x",encoding="utf-8") as f:
    json.dump(request,f,ensure_ascii=False,indent=2)
print(output)
```

Replace the example keyword `coffee` with your research keyword. Build the request file locally, then send the request once with curl:

```bash
python3 build_kuaishou_search.py "coffee" kuaishou-request.json
curl --fail-with-body -sS https://api.beatapi.io/v1/social-data/call \
  -H "Authorization: Bearer $BEATAPI_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary @kuaishou-request.json \
  -o kuaishou-search-page-1.json
```

Save the request ID, the inputs, the query time, the original response and the returned state. An HTTP success does not mean the material is complete: check the posts inside `kuaishou-search-page-1.json` before you select any.

## 3. Which posts deserve more reading?

Read the comments of posts that demonstrate the preparation steps. Judge each post by topic, format and the steps the post shows, and record for each candidate the post ID, the source, the reason for selecting or excluding the post, and the material still missing.

1. Use titles and descriptions for the first pass.
2. Watch the video or view the images when you compare how two posts demonstrate a step.
3. Shortlist a post that uses the same ingredients and shows the prep from start to finish. Save a popular plating-only clip as a filming reference instead.
4. Link each candidate to the candidate's source and selection reason by post ID. When the same post appears on several result pages, keep one candidate row and record every source page.

## 4. Read selected comments

Pass the verified `photo_id` of each shortlisted post to `kuaishou.app.fetch_video_comment`, with an empty `pcursor` for the first page. Note the viewers' questions and conditions. When a question needs the reply thread, expand the replies as described in [comment context](/faq/kuaishou-comment-pagination).

“How do I know this step is finished?” and “Would another pan work?” become explanation questions. “It finally worked” is an experience: keep the comment and record any condition the commenter gives. Attach the original wording to each theme. Likes on a comment do not show that viewers agree on a method.

## 5. Add material deliberately

1. Within one round, keep the keyword, ordering, period and duration unchanged.
2. For the next page, pass the `pcursor` returned by the previous page and save the response to a new file.
3. When you change any filter, start again from an empty `pcursor` and save the result as a separate observation.
4. Stop and record the reason when `pcursor` is missing or repeats, a request fails, or you reach the planned page count.

After each page, check whether the page adds a new step or condition. Once the material supports the brief, read the selected posts closely and fetch more only for a specific gap. To find creators, use the separate user search; the post filters in step 1 do not filter accounts.

## 6. Hand off editorial reasons

Organize each row as “viewer question—excerpt—post—conditions—useful angle—open item”. When several comments ask about the same omitted step, first check whether a reply already answers the question; if no reply does, propose a tutorial that explains the step.

For the assistant:

> Select cooking posts that actually explain preparation, retaining selection reasons. Read their comments and preserve questions and conditions. Identify steps worth explaining and material still needed, attaching sources rather than copying popular titles.

Export one row per question your next tutorial could answer. For example, “When using a smaller pan, how can I tell when the first batch is cooked through?” Include the source post and comment references, plus details to verify such as pan size and ingredient quantity. Each search page, each comment page on a shortlisted post and each reply page is a separate paid request; see current [pricing](https://beatapi.io/pricing).

[Share links and identity](/faq/kuaishou-identifiers) · [Comment continuation and replies](/faq/kuaishou-comment-pagination)