DataNavoAPI / ANSWERS / WEIBO

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.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

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.

02

Relevant contracts

CapabilityObjectShapePagination
weibo.posts.getPostitemNo cursor
weibo.users.getAccountitemNo cursor
03

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.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringOptional / conditionalPost ID, a string of digits. With only a link or a share text, give it as url—"5352571897120856"
GETurlstringOptional / conditionalLink 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——
GETviewstringOptional / conditionalHow much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`).["compact","standard","full"]—
GETfieldsarrayOptional / conditionalReturn only these fields of each item, by path (`author.name`).maxItems: 64—
04

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"
  }
}
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗