Catalog

Weibo API

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

Endpoints6Providers1From · post$1.20/1k req · TigerFull breakdownRead docs
Uptime
98.84%
30d · 86 calls
Requests
86
30d · weekly, last 12 wks
Response
1.5s
median · 30d
POST

Post

Most used
/v1/run/weibo.postweibo.post
Fetch a public Weibo post by ID with normalized author and engagement data.
29 /mo
100.00%
968ms p50
1
price$1.20/1k req
Tiger
POST

Search

/v1/run/weibo.searchweibo.search
Search public Weibo posts with optional result, media, and time filters.
27 /mo
▲800%
100.00%
2246ms p50
1
price$1.20/1k req
Tiger
POST

Hot search

/v1/run/weibo.hot_searchweibo.hot_search
Get the complete current Weibo hot-search ranking with labels and heat values.
10 /mo
▲900%
90.00%
1343ms p50
1
price$1.80/1k req
Tiger
POST

User posts

/v1/run/weibo.user_postsweibo.user_posts
List public posts from a Weibo user with normalized author and engagement data.
8 /mo
100.00%
2088ms p50
1
price$1.20/1k req
Tiger
POST

Post comments

/v1/run/weibo.post_commentsweibo.post_comments
List first-level comments on a public Weibo post with pagination.
6 /mo
▲100%
100.00%
1284ms p50
1
price$1.20/1k req
Tiger
POST

Profile

/v1/run/weibo.profileweibo.profile
Fetch a public Weibo profile by user ID with normalized audience and account data.
6 /mo
100.00%
1012ms p50
1
price$1.20/1k req
Tiger

About the Weibo API

Open an endpoint for its live route, a copy-paste cURL and a sample response.

Measured performance

What the Weibo API actually does

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

98.8%
of calls succeeded (86 calls)
Succeeded on first lane 98.8%Failed 1.2%
Response time estimate (85 calls across endpoints)
Weighted p50 estimate
1.5s
Request-weighted average of endpoint p50 values, not a combined request percentile
Weighted p99 estimate
2.9s
Request-weighted average of endpoint p99 values, not a combined request percentile

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, 98.8% of Weibo calls through AnyAPI succeeded, with a request-weighted median response time of 1.5 seconds across 86 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 and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

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, 98.8% of Weibo calls through AnyAPI succeeded, with a request-weighted median response time of 1.5 seconds across 86 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.