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

# Weibo questions

> Choose the Weibo action for keyword search, trending boards, a selected post, its comments or an account timeline.

To find posts about a subject, use [keyword search](/faq/weibo-keyword-search). To see what people discuss today, read [trending searches](/faq/weibo-hot-search). With a specific post, [verify the post and read its comments](/faq/weibo-comment-research) with `weibo.web_v2.fetch_post_detail` and `weibo.web_v2.fetch_post_comments`.

## Search and discovery

* [Keyword search](/faq/weibo-keyword-search)
* [Search pagination](/faq/weibo-search-pagination)

## Trends and research

* [Hot search](/faq/weibo-hot-search)
* [Trend categories](/faq/weibo-trend-categories)
* [Local trends](/faq/weibo-local-trends)
* [Trend pagination](/faq/weibo-trend-pagination)

## Links and identities

* [Post and user identifiers](/faq/weibo-identifiers)

## Research recovery

* [Resume interrupted research](/faq/weibo-research-recovery)

## Video and metrics

* [Video play-count reports](/faq/weibo-video-metrics)

## Comments and user questions

* [Comments to user questions](/faq/weibo-comment-research)

## Choose between a post, its comments and an account timeline

To review questions after a product launch, read the announcement post and selected comments first, then find related posts from the same account. Each action below is a `POST https://api.beatapi.io/v1/social-data/call` request with a BeatAPI Bearer credential and a JSON body containing the action and parameters. The post ID and the account UID are different identifiers; verify each one with the [identifier guide](/faq/weibo-identifiers).

| Goal                        | action                             | Example first params                           |
| --------------------------- | ---------------------------------- | ---------------------------------------------- |
| Read a selected long post   | `weibo.web_v2.fetch_post_detail`   | `{"id":"<post_id>","is_get_long_text":"true"}` |
| Sample comments on the post | `weibo.web_v2.fetch_post_comments` | `{"id":"<post_id>","count":10,"max_id":""}`    |
| Check posts by that account | `weibo.web_v2.fetch_user_posts`    | `{"uid":"<uid>","page":1,"feature":0}`         |

For each response, save the original response, the request ID and the object ID, then check:

1. `weibo.web_v2.fetch_post_detail` returned the full text you need.
2. The comments from `weibo.web_v2.fetch_post_comments` belong to the intended post.
3. The posts from `weibo.web_v2.fetch_user_posts` match the account and the dates you compare.

The three actions have no shared published results-array schema, so map the fields of each actual response. For the next comment page, pass the returned `max_id`. For the next timeline page, use the `page` parameter of `weibo.web_v2.fetch_user_posts` or the returned `since_id`; do not mix the two cursors. To discover topics first, read [hot search](/faq/weibo-hot-search) and then select posts to read.

## Related content

[Weibo task guides](/guides/weibo)

## Give your connected assistant a concrete task

> Study public reactions to this headset firmware update. Search one batch, retaining actual publication times and model references. Retrieve selected long posts when excerpts are insufficient, and read relevant comments. Distinguish announcements, reposted accounts and personal experiences and cite each finding.

The assistant chooses posts from the search preview. For a quote, the assistant reads the saved result or retrieves the specific post. Ask the assistant to report which material it reviewed and the actual coverage. [Task walkthrough](/guides/weibo-python-research) · [Connection and result reading](/faq/assistant-social-research).