Weibo post_reposts API

Weibo post_reposts data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

1 documented endpoints
GET /v1/weibo/posts/{id}/reposts

Contract summary (English): List Weibo post reposts (capability weibo.post_reposts)

Normalized response entity: weibo/post_reposts
capability: weibo.post_reposts

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

Feed content-analysis pipelines with structured {{platform}} posts: text, metrics, timestamps and media references.
Power moderation, research and monitoring workflows that need the original content plus engagement counts.
Archive {{platform}} content as stable, normalized JSON instead of brittle page scraping.

Response fields

Weibo weibo.post_reposts response (normalized envelope)

Response envelope of the /v1/weibo weibo.post_reposts capability. Cursor is opaque and platform-independent; page size follows the request's `limit` parameter (1..100, default 20).

Field	Type	Required	Description
data	post[]	Required	—
next_cursor	string \| null	Required	Opaque pagination cursor; null when the list is exhausted.
meta.request_id	string	Required	—
meta.freshness.mode	cache \| default \| live	Required	—
meta.freshness.age_seconds	integer \| null	Optional	—
meta.freshness.source_layer	cache \| db \| upstream	Required	—
meta.freshness.stale	boolean	Optional	—
meta.billing.cache_hit	boolean	Required	—
meta.billing.amount_credits	integer	Required	Credits actually charged for this request (the settlement unit; 1 credit = $0.0001, permanent).

Field notes are shown in the contract's original English.

Response meta

Field	Type	Required	Description
mode	cache \| default \| live	Required	Effective mode after merging param > max_age > source policy (D-004).
age_seconds	integer \| null	Optional	Age of served data; null when unknown.
source_layer	cache \| db \| upstream	Required	Which layer served the response (PRD §10).
stale	boolean	Optional	True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_credits	integer	Required	Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hit	boolean	Required	—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/weibo/posts/{id}/reposts

curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/weibo/posts/1842951234567890123/reposts"

{
  "data": [
    {
      "id": "5551000000001001",
      "platform": "weibo",
      "type": "post",
      "author": {
        "id": "6605000122",
        "username": "微博数据站",
        "display_name": "微博数据站",
        "verified": true
      },
      "text": "一条关于数据 API 的微博。",
      "created_at": "2026-09-17T04:34:56Z",
      "metrics": {
        "likes": 8230,
        "comments": 1204,
        "shares": 988
      },
      "attachments": [
        {
          "type": "photo",
          "url": "https://cdn.example.com/images/weibo-5551000000001001-1.jpeg"
        },
        {
          "type": "photo",
          "url": "https://cdn.example.com/images/weibo-5551000000001001-2.jpeg"
        }
      ],
      "fetched_at": "2026-09-21T09:00:00Z"
    }
  ],
  "next_cursor": null,
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 200,
      "cache_hit": false
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

Which content fields are included?

The normalized content entity — text, author, timestamps, engagement metrics and media references — as documented in the field table below, plus freshness and billing metadata.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the post_reposts capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.

View pricing Browse all APIs