> 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 identify a shared Weibo post before reading its text or comments?

> Distinguish user uid, numeric post IDs and desktop bid, then use verified identities for text or comments with original sources preserved.

Identify the post by its numeric post ID, then pass that ID as `id` to `weibo.web_v2.fetch_post_detail` for the text or to `weibo.web_v2.fetch_post_comments` for the comments. A Weibo profile's `uid` identifies an account, a numeric `mid` identifies a post, and an alphanumeric `bid` commonly appears at the end of a desktop post URL.

For example, when a colleague shares a service notice, check the author and the announcement text first. With a verified post ID, go straight to the comments if comments are what you need. Fetch the long text when you need to check the full notice.

## What do the identifiers mean?

| Information                                                        | Meaning and use                                                                             |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
| Digits after `weibo.com/u/`                                        | User `uid` for profile and account-content actions                                          |
| Digits after mobile `/detail/` or `/status/`                       | Preserve as a string when confirmed as the intended numeric post ID                         |
| Final alphanumeric segment of desktop `weibo.com/<user>/<segment>` | Common `bid` representation, distinct from user uid and an already verified numeric post ID |
| Post identifier in saved search or other responses                 | Reuse after checking author and content, keeping original fields and source                 |

Store identifiers in spreadsheet text columns so that spreadsheet software does not convert the digits. Keep the original link for later review. When a link path contains both a user segment and a post segment, do not pick the post by the longest number.

## What comes next with a verified post ID?

For the full text, pass the post ID as `id` to `weibo.web_v2.fetch_post_detail`, with `is_get_long_text` set to the string `"true"`:

```json
{
  "action": "weibo.web_v2.fetch_post_detail",
  "params": {"id": "<confirmed_post_id>", "is_get_long_text": "true"}
}
```

For the comments only, pass the same post ID as `id` to `weibo.web_v2.fetch_post_comments`. The first `max_id` is empty:

```json
{
  "action": "weibo.web_v2.fetch_post_comments",
  "params": {"id": "<confirmed_post_id>", "count": 10, "max_id": ""}
}
```

Send the chosen JSON to `POST https://api.beatapi.io/v1/social-data/call` with normal BeatAPI Bearer authentication. Choose the action by the material you need; a comment request does not require a detail request first.

## What if you only have a desktop code or pasted share text?

Find the numeric post ID first, because `weibo.web_v2.fetch_post_detail` and `weibo.web_v2.fetch_post_comments` accept `id` and have no `url` parameter. BeatAPI has no recorded Weibo share-link expansion or `bid` conversion, so pasting share text as another service allows is not supported here.

1. If you have saved search or account results, find the intended post in those results and confirm the post ID against the author and the text.
2. Otherwise, ask for the post's numeric mobile link, which contains the post ID.
3. If only an unconfirmed code remains, record the code as an open item. Do not substitute a user `uid` for the post ID.

[Keyword search](/faq/weibo-keyword-search) can help locate the post again, but posts with identical titles and reposted text still need verification.

## What should the next researcher receive?

Hand over the original link, the verified post ID, the author `uid` when available, the action and inputs, the actual time and the request ID. `weibo.web_v2.fetch_post_detail` and `weibo.web_v2.fetch_post_comments` have no recorded fixed output schema: inspect the actual response before assigning author, text and comment relationships, and do not assume universal keys such as `author.id`.

For example, hand off the comment “I cannot find this step's entry” together with the announcement source and the original comment. If the comment comes from a user's repost of the announcement, state that the comment belongs to the repost, not to the official announcement.

Prompt for the assistant:

> Confirm this service-announcement post and preserve original link, post ID and author separately. Reuse verified IDs and retrieve only needed text or comments. Keep operating questions with original excerpts and sources; leave unresolved links as open items rather than substituting namesakes.

Budget the selected detail requests and comment pages with current [pricing](https://beatapi.io/pricing). Reuse saved responses for further reading.