# How should I distinguish Weibo mid, uid and bid?

How should I distinguish Weibo mid, uid and bid? Follow concrete contracts, examples and reviewable steps using Weibo.

Canonical page: https://datanavoapi.com/en/answers/weibo-mid-uid-bid/

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

## Answer

Start by inspecting the contracts and local samples for Weibo post detail, Weibo user profile. Establish the input for weibo.posts.get, then check whether its post object contains the fields your task needs.

Treat identifiers as typed values: content, account, comment and share-link identifiers are not interchangeable. Preserve the original string instead of converting large IDs to JavaScript numbers, and submit only fields explicitly defined by the contract.

## Relevant contracts

| Capability | Object | Shape | Pagination |

| --- | --- | --- | --- |

| weibo.posts.get | Post | item | No cursor |

| weibo.users.get | Account | item | No cursor |

- [Weibo post detail](https://datanavoapi.com/en/apis/weibo/posts/get/)
- [Weibo user profile](https://datanavoapi.com/en/apis/weibo/users/get/)

## Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

- GET: supply exactly one of id / url.

| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |

| --- | --- | --- | --- | --- | --- | --- |

| GET | id | string | Optional / conditional | Post ID, a string of digits. With only a link or a share text, give it as url | — | "5352571897120856" |

| GET | url | string | Optional / conditional | Link to the post, pasted as it is: the site's https://weibo.com/<user>/… (digits or letters after it), the phone site's https://m.weibo.cn/detail/… or /status/…, or a whole share text with one of these in it | — | — |

| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |

| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |

## Complete one verification

Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.

```json
{
  "capability": "weibo.posts.get",
  "method": "GET",
  "params": {
    "id": "5352571897120856"
  }
}
```

## Related pages

- [Weibo post detail](https://datanavoapi.com/en/apis/weibo/posts/get/)
- [Weibo user profile](https://datanavoapi.com/en/apis/weibo/users/get/)
- [Weibo APIs](https://datanavoapi.com/en/apis/weibo/)
- [Weibo MCP](https://datanavoapi.com/en/mcp/weibo/)
- [Post fields](https://datanavoapi.com/en/docs/objects/post/)
- [Organize Weibo discussions with Python](https://datanavoapi.com/en/guides/weibo-api-python/)
- [Account review workflow](https://datanavoapi.com/en/skills/account-audit/)
- [How can AI assist an account review?](https://datanavoapi.com/en/answers/ai-account-audit-and-review/)
- [How should I record and investigate a Weibo 432 error?](https://datanavoapi.com/en/answers/weibo-432-client-error/)

[中文](https://datanavoapi.com/answers/weibo-mid-uid-bid/)
