FetchPI
Log in
← Browse all APIs

Weibo search_posts API

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

  • 1 documented endpoints
  • GET /v1/weibo/search/posts

Contract summary (English): Search Weibo posts (capability weibo.search_posts)

Normalized response entity
weibo/search_posts
capability
weibo.search_posts

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

Use cases

  • Find {{platform}} content and accounts matching a keyword, with normalized results ready for scoring.
  • Follow trending topics and hot lists to catch emerging conversations early.
  • Alert on search and trend queries so your team sees shifts as they happen.

Response fields

Weibo weibo.search_posts response (normalized envelope)

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

FieldTypeRequiredDescription
datapost[]Required—
next_cursorstring | nullRequiredOpaque pagination cursor; null when the list is exhausted.
querystringOptionalThe echoed search query.
meta.request_idstringRequired—
meta.freshness.modecache | default | liveRequired—
meta.freshness.age_secondsinteger | nullOptional—
meta.freshness.source_layercache | db | upstreamRequired—
meta.freshness.stalebooleanOptional—
meta.billing.cache_hitbooleanRequired—
meta.billing.amount_creditsintegerRequiredCredits 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

FieldTypeRequiredDescription
modecache | default | liveRequiredEffective mode after merging param > max_age > source policy (D-004).
age_secondsinteger | nullOptionalAge of served data; null when unknown.
source_layercache | db | upstreamRequiredWhich layer served the response (PRD §10).
stalebooleanOptionalTrue when stale data was served under stale_if_error / SWR (D-004).
billing.amount_creditsintegerRequiredMicro-USD (1e-6 USD) actually charged for this request.
billing.cache_hitbooleanRequired—

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

Example request & response

GET/v1/weibo/search/posts
curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/weibo/search/posts?q=meshdata"
{
  "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,
  "query": "数据",
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 300,
      "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

What is the difference between cache and live freshness?

cache answers from the stored snapshot without touching the upstream; live queries fresher data and may cost extra credits — see the freshness section of the docs.

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