DataNavoAPI / APIS / WEIBO

Weibo user profile

Weibo user profile: inspect inputs, account fields, pagination and limits, then run a local simulated request.

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

What this capability does

Weibo user profile uses /v1/weibo/users/get; GET returns data.item with account objects.

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

  • Capability: weibo.users.get
  • Pagination: no cursor pagination; do not repeatedly request another page.
02

Input contract

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

  • Only send fields defined for this method; unknown fields are rejected before execution.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringRequiredUser ID (uid), a string of digits: the number after weibo.com/u/ in a profile link—"2803301701"
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—
03

Try it locally

Use demo to inspect the fields, then explicitly select simulated with a customer test key to exercise settlement. Never put a customer key in a URL.

json
{
  "capability": "weibo.users.get",
  "method": "GET",
  "params": {
    "id": "2803301701"
  }
}
04

Output fields and interpretation

The account object permits missing or null values; do not replace missing measurements with zero. This table shows the main structure; the object reference covers nested fields.

FieldTypeMeaningSource scope
idstring | nullIDWeibo
usernamestring | nullHandleWeibo
namestring | nullDisplay nameWeibo
urlstring | nullLink to the profileWeibo
biostring | nullBioWeibo
avatar_urlstring | nullAvatar (standard view and up)Weibo
verifiedboolean | nullWhether the account is verified (standard view and up)Weibo
created_atstring | nullWhen the account was created (standard view and up)Weibo
metricsobject | nullAccount countsWeibo
metrics.followersinteger | nullFollowersWeibo
metrics.followinginteger | nullFollowingWeibo
metrics.postsinteger | nullPosts publishedWeibo
approximatearray | nullWhich numbers of this item are approximate or lower bounds; absent when all are exactWeibo
approximate[].fieldstring | nullPath of the field, such as metrics.viewsWeibo
approximate[].kindstring | nullApproximate, or a lower boundWeibo
extobject—Weibo
ext.likesinteger | nullLikes received in all, on videos, articles and posts: the number the profile shows (full view)Weibo
ext.verified_reasonstring | nullWhat the verification says, in the platform's words (百大UP主 or 知名游戏UP主, say); null when not verified (full view)Weibo
ext.genderstring | nullThe gender the user gives on the profile: female or male; null where none is given (full view)Weibo
ext.interactionsinteger | nullReposts, comments and likes in all: the number the profile shows, the sum of the three below (full view)Weibo
ext.comments_receivedinteger | nullComments received on all of the account's posts (full view)Weibo
ext.reposts_receivedinteger | nullTimes the account's posts have been reposted, in all (full view)Weibo
ext.verified_typestring | nullKind of verification: person (an individual, the orange or gold V) or organization (the blue V of a company, a media outlet, a government body and the like); null when not verified (full view)Weibo
ext.locationstring | nullThe region given on the profile (北京, 广东 深圳, say; 其他 where none was given), not the IP location (full view)Weibo
05

Unavailable fields

These published contract notes describe the capability boundary; fixtures do not establish live availability.

FieldReason
usernameplatform
created_atcapability
06

Limits and checks

A successful request does not establish full coverage. Preserve the request ID, observation time, parameters and cursor, and inspect the returned items before analysis.

Local simulation uses TEST credits only. Real provider calls, real payments and external email are disabled. Historical reference-site prices are not DataNavoAPI prices.

  • Verify media URLs, counts and optional fields individually.
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 ↗