Weibo scraper API
The InsightSocial Weibo API has 6 endpoints, from 10 credits a call. A profile call costs 10 credits, about $0.01 on Pro, and your first 10 calls up to 100 credits each are free.
The Weibo scraper API for public profiles, posts, comments and keyword search, as JSON, plus the live hot-search ranking. No Weibo Open Platform app and no OAuth.
6 endpoints · from 10 credits a call · 10 free calls up to 100 credits each · no credit card
curl "https://api.insightsocial.app/v1/weibo/profile?user_id=1234567890" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
What Weibo data can you get?
Public Weibo data only, returned in the same JSON envelope as every other platform.
Profiles
Name, bio, follower, following and post counts, verification and its reason, location and website.
Posts
An account's recent posts page by page, and one post in full, long text included, with like, comment and repost counts.
Comments
First-level comments under a post with text, author, likes, reply count and time.
Weibo API endpoints
All 6 Weibo endpoints and their price in credits. Every one has a fixed price.
| Endpoint | Credits | What it returns |
|---|---|---|
| /post | 10 | Returns one public Weibo post: its text, author, like, comment and repost counts, image count and publish time. |
| /profile | 10 | Returns a public Weibo account: name, bio, avatar, follower, following and post counts, verification, location and website. |
| /user/posts | 10 | Returns a page of an account’s recent public posts, each with text, engagement counts and publish time. |
| /post/comments | 10 | Returns a page of first-level comments on a post, each with text, author, likes, reply count and time. |
| /search | 10 | Returns public Weibo posts matching a keyword, each with text, author, engagement counts and URL. |
| /trending | 10 | Returns the current Weibo hot-search ranking: each topic’s keyword, rank, heat and label, pinned topics marked. |
Parameters, response fields and examples for each endpoint are in the Weibo API reference.
InsightSocial vs the official Weibo API
The Weibo Open Platform needs a registered app and OAuth 2.0 user authorization, and its advanced interfaces need a separate application to Weibo.
| InsightSocial API | Official Weibo API | |
|---|---|---|
| Setup | Sign in and copy a key | Developer account, app (App Key) and OAuth 2.0 |
| Approval | None | App review, plus an application for each advanced interface |
| Users | No user has to authorize you | Each user authorizes your app through OAuth 2.0 |
| Cost per call | 10 credits | No per-call price; access is set by app review and interface permissions |
The official API is the right tool for posting, messaging or managing accounts you own. This one is read-only public data.
How much does the Weibo API cost?
Weibo calls start at 10 credits. Every endpoint's price is in the table above and in the free GET /v1/endpoints catalogue, so you know the cost before you call. Pro's 10,000 monthly credits cover about 1,000 profiles at 10 credits each.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Repeats and retries
A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
One balance
API calls and Chrome extension exports share the same credits. The free plan includes 500 a month.
Not writing code?
Connect InsightSocial to Claude or ChatGPT and ask for Weibo data in plain English. Same account, same credits.
Weibo API: frequently asked questions
Yes, the Weibo Open Platform. It needs a registered app with an App Key, OAuth 2.0 authorization from users, and a separate application for each advanced interface. The InsightSocial API reads public Weibo profiles, posts and comments with one key.
Yes. /v1/weibo/trending returns the current hot-search ranking: each topic's keyword, rank, heat and label, with pinned topics marked. It is a beta endpoint, so its fields may change.
/v1/weibo/search returns public posts for a keyword, page by page. search_type narrows it to hot, original, verified, media or viewpoint posts, and include_type to posts with pictures, video, music or links.
The numbers in the URL. /v1/weibo/profile and /v1/weibo/user/posts take the numeric user id from weibo.com/u/<id>, and /v1/weibo/post and /v1/weibo/post/comments take the post id from the post URL.
Every Weibo endpoint is 10 credits a call, including a page of comments or search results and the hot-search ranking. Calls that fail or find nothing are free.
No. There is no Weibo app, OAuth flow or review. One API key in the x-api-key header works for Weibo and the other 60 platforms.
Yes. Your first 10 calls priced at 100 credits or less are free, and the free plan includes 500 credits every month. No credit card is needed to get a key.
60 requests a minute and 10 requests in flight at once, per API key. Going over either returns a 429 with a Retry-After header, and a rejected request costs nothing. There is no daily quota: past those two limits, your credit balance is what bounds volume.
List endpoints return rows in data.items and a pagination object with next_cursor and has_more. Send next_cursor back unchanged as the cursor parameter for the next page, and stop when has_more is false. A handful of endpoints page with their own parameter instead; their reference pages name it.
No. A call that errors or finds nothing costs 0 credits. A live fetch costs the endpoint's price, or for a metered endpoint what it actually read. A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
A call fetches live unless a recent copy is in the shared cache, and every response says which with the cached field; a cached answer costs 2 credits. Add fresh=1 or send Cache-Control: no-cache to skip the cache; that call is charged at the normal price.
Collecting publicly available data is generally treated differently from accessing private data, but the answer depends on your jurisdiction, Weibo's terms and what you do with personal data afterwards. The API reads public data only. Talk to a lawyer for anything commercial.
Weibo API guides
The same key works for 60 more platforms
- TikTok scraper API
- LinkedIn scraper API
- Twitter/X scraper API
- YouTube scraper API
- Reddit scraper API
- Pinterest scraper API
- Bluesky scraper API
- Truth Social scraper API
- Snapchat scraper API
- Telegram scraper API
- Twitch scraper API
- Kick scraper API
- Rumble scraper API
- Kwai scraper API
- Douyin scraper API
- Xiaohongshu (RedNote) scraper API
- Quora scraper API
- TikTok Shop scraper API
- Zhihu scraper API
- Substack scraper API
- Nextdoor scraper API
- Amazon scraper API
- App Store scraper API
- Apple Music scraper API
- Behance scraper API
- Dailymotion scraper API
- Deezer scraper API
- DEV Community scraper API
- Discord scraper API
- Dribbble scraper API
- Fandom scraper API
- Flickr scraper API
- GitHub scraper API
- Google Ads Transparency scraper API
- Google News scraper API
- Google Trends scraper API
- Gumroad scraper API
- Hacker News scraper API
- Hugging Face scraper API
- Ko-fi scraper API
- Lemmy scraper API
- Letterboxd scraper API
- Linktree scraper API
- Lnk.Bio scraper API
- Mastodon scraper API
- Medium scraper API
- MyAnimeList scraper API
- npm scraper API
- Polymarket scraper API
- Product Hunt scraper API
- Shopify scraper API
- SoundCloud scraper API
- Spotify scraper API
- Stack Overflow scraper API
- Stan Store scraper API
- Steam scraper API
- Vimeo scraper API
- Wikipedia scraper API
- Yahoo Finance scraper API
- Yelp scraper API