Catalog

Weibo API

Weibo data through one normalized API - per-request USD pricing and no subscriptions.

Endpoints6Providers1From · search$1.20/1k req · TigerFull breakdownRead docs
Uptime
100.00%
30d · 4 calls
Requests
4
30d · weekly, last 12 wks
Response
2.3s
median · 30d

Measured performance

What the Weibo API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (4 calls)
Succeeded on first lane 100.0%
Response time (4 calls)
Typical (p50)
2.3s
Half of requests finish within 2.3s
p99 response time
2.5s
p99 response time: 99% of requests finish within 2.5s

FAQ

About the Weibo API

The AnyAPI Weibo API returns Weibo data as normalized JSON across 6 endpoints: hot search, post, post comments, profile, search, and user posts. You call one endpoint per job with a single key, and AnyAPI returns one normalized schema whichever source serves it. Pricing is in US dollars, from $1.20 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Weibo calls through AnyAPI succeeded, with a median response time of 2.3 seconds across 4 measured calls.

Pricing is in US dollars, from $1.20 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

6 endpoints: hot search, post, post comments, profile, search, and user posts. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Weibo endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Weibo calls through AnyAPI succeeded, with a median response time of 2.3 seconds across 4 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.