# Weibo post detail

Weibo post detail: inspect inputs, post fields, pagination and limits, then run a local simulated request.

Canonical page: https://datanavoapi.com/en/apis/weibo/posts/get/

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

## What this capability does

Weibo post detail uses /v1/weibo/posts/get; GET returns data.item with post objects.

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

- Capability: weibo.posts.get
- Pagination: no cursor pagination; do not repeatedly request another page.

## 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 | — |

## 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.posts.get",
  "method": "GET",
  "params": {
    "id": "5352571897120856"
  }
}
```

- [Open this capability in the console](https://datanavoapi.com/console/?mode=demo&capability=weibo.posts.get&method=GET&params=%7B%22id%22%3A%225352571897120856%22%7D)

## Output fields and interpretation

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

| Field | Type | Meaning | Source scope |

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

| id | string \| null | ID; pass it unchanged to the get endpoint | Weibo |

| url | string \| null | Link that opens the post | Weibo |

| type | string \| null | Content format | Weibo |

| title | string \| null | Title | Weibo |

| text | string \| null | Body text | Weibo |

| lang | string \| null | Language of the text (standard view and up) | Weibo |

| published_at | string \| null | When it was published | Weibo |

| author | object \| null | Author | Weibo |

| author.id | string \| null | Author's account ID | Weibo |

| author.username | string \| null | Author's handle | Weibo |

| author.name | string \| null | Author's display name | Weibo |

| author.avatar_url | string \| null | Author's avatar (standard view and up) | Weibo |

| author.verified | boolean \| null | Whether the author is verified (standard view and up) | Weibo |

| author.followers | integer \| null | Author's follower count (standard view and up) | Weibo |

| metrics | object \| null | Engagement counts | Weibo |

| metrics.likes | integer \| null | Likes | Weibo |

| metrics.comments | integer \| null | Comments | Weibo |

| metrics.shares | integer \| null | Shares | Weibo |

| metrics.favorites | integer \| null | Saves | Weibo |

| metrics.views | integer \| null | Views | Weibo |

| metrics.reposts | integer \| null | Reposts | Weibo |

| images | array \| null | Image addresses (standard view and up) | Weibo |

| hashtags | array \| null | Hashtags, without the # (standard view and up) | Weibo |

| mentions | array \| null | Accounts mentioned in the text (standard view and up) | Weibo |

| mentions[].id | string \| null | Account ID (standard view and up) | Weibo |

| mentions[].username | string \| null | Handle (standard view and up) | Weibo |

| mentions[].name | string \| null | Display name (standard view and up) | Weibo |

| is_pinned | boolean \| null | Whether the author pinned it (standard view and up) | Weibo |

| post_id | string \| null | ID of the thread's root post when this is a reply; otherwise null | Weibo |

| parent_id | string \| null | ID of the item it replies to directly; otherwise null | Weibo |

| root_id | string \| null | ID of the first-level reply its thread hangs under | Weibo |

| approximate | array \| null | Which numbers of this item are approximate or lower bounds; absent when all are exact | Weibo |

| approximate[].field | string \| null | Path of the field, such as metrics.views | Weibo |

| approximate[].kind | string \| null | Approximate, or a lower bound | Weibo |

| ext | object | The platform's own fields (full view). | Weibo |

| ext.ip_location | string \| null | IP location as the platform shows it (full view) | Weibo |

| ext.text_truncated | boolean \| null | Whether the text is cut short: a long post comes with its beginning only in lists and search; get the post for the whole (full view) | Weibo |

| ext.reposted_id | string \| null | ID of the post it reposts; null when it is not a repost (full view) | Weibo |

- [Complete object reference](https://datanavoapi.com/en/docs/objects/post/)

## Unavailable fields

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

| Field | Reason |

| --- | --- |

| title | platform |

| lang | capability |

| author.username | platform |

| author.followers | capability |

| metrics.shares | platform |

| metrics.favorites | capability |

| mentions | capability |

| is_pinned | capability |

| post_id | platform |

| parent_id | platform |

| root_id | platform |

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

## Related pages

- [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/)
- [How should I record and investigate a Weibo 432 error?](https://datanavoapi.com/en/answers/weibo-432-client-error/)
- [Which APIs cover Weibo accounts, posts, comments and trends?](https://datanavoapi.com/en/answers/weibo-data-apis/)
- [How should I distinguish Weibo mid, uid and bid?](https://datanavoapi.com/en/answers/weibo-mid-uid-bid/)
- [How should I separate Weibo play counts from engagement?](https://datanavoapi.com/en/answers/weibo-video-play-count/)

[中文](https://datanavoapi.com/apis/weibo/posts/get/)
