Fetch public Weibo accounts, posts, comments, search results and the hot-search list as structured JSON with one SocialCrawl API key. Same Author, Post and Comment schema as every other platform. Reads are priced in credits.
8 active endpoints. Accounts, posts, comments, search and trending.
Eight read endpoints for public Weibo data. Look up an account, list its posts, read comments and replies, search posts and accounts, or pull the hot-search list.
/v1/weibo/profileOne account by handle, numeric id or profile link. Returns the screen name, bio, verification and its reason, exact follower, following and post counts, location, gender, birthday and the date the account was created. Standard tier (1 credit).
handle, id, url
/v1/weibo/profile/postsAn account's posts, newest first, up to 50 a page. Each post has exact repost, comment and like counts, the province or country it was posted from, topics and media. Cursor paging reaches back through roughly the newest 2,000 posts. Long posts are shortened here. Advanced tier (5 credits).
handle, id, url, media_only, limit, cursor
/v1/weibo/postOne post in full. Returns the complete text, author, time, the province or country it was posted from, exact repost, comment, like and read counts, topics, every photo and the video. Standard tier (1 credit).
url
/v1/weibo/post/commentsComments on a post, most liked first (hot) or newest first (latest). Each has its text, time, the province it was posted from, likes, reply count and the author with an exact follower count. Weibo stops very large threads at a few hundred comments. Advanced tier (5 credits).
url, sort, limit, cursor
/v1/weibo/comment/repliesThe replies under one comment, oldest first. Each names the comment it answers in comment.parent_id and carries its province, likes and author. Take comment_id from the post comments route. Advanced tier (5 credits).
comment_id, limit, cursor
/v1/weibo/searchPublic posts matching a keyword or a #topic#, newest first, up to 50 a page. since and until read a fixed period, back for years. Tabs include latest, all, original, verified, top, hot, videos, media and images. These are the posts Weibo's own search shows, so a search is not a census. Advanced tier (5 credits).
query, tab, since, until, limit, cursor
/v1/weibo/search/usersUp to 50 accounts matching a name or keyword, with screen name, bio, verification and its reason, post count and gender. Follower counts are rounded in search, so author.followers is null here. The profile route returns the exact figure. Advanced tier (5 credits).
query, limit
/v1/weibo/trendingWeibo's live hot-search list. Each topic has its rank, title, exact heat score, category, new or hot badge and the time it joined the list. Paid placements are left out unless include_promoted is true. Advanced tier (5 credits).
include_promoted, limit
Returns one Weibo account: name, bio, verification and its reason, exact follower, following and post counts, location, gender, birthday, and the date it was created.
Use it to size up an account before pulling its posts, or to get the exact follower figure that account search leaves out.
1 credit
$ curl https://www.socialcrawl.dev/v1/weibo/profile?id=2803301701 \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responseWeibo is a normal SocialCrawl data surface. You call GET /v1/weibo/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Send your key in the x-api-key header. No Weibo account or developer app is needed for public reads. The same key works across SocialCrawl platforms.
Send a handle, id, url, query or comment_id as a query string, depending on the route. Account routes accept one of handle, id or url. Formats are validated before any charge.
Account profile and post detail cost 1 credit. Every other Weibo route costs 5 credits. Cache hits cost 0.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.
Most products find an entity first, then deepen into detail and reviews only when needed.
GET /v1/weibo/search/users?query=…AuthorList of matching accounts
Search returns screen names and ids; follower counts are rounded here.
GET /v1/weibo/profile?id=…Author with exact follower, following and post counts
The profile route returns the exact figures that search rounds.
GET /v1/weibo/profile/posts?id=…PostList, newest first, up to 50 a page
Cursor paging reaches back through roughly the newest 2,000 posts.
GET /v1/weibo/post/comments?url=…CommentList, hot or latest
Comments show reader reaction, and replies are one more call away.
GET /v1/weibo/profile?id=2803301701
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/weibo/profile/posts?id=2803301701&limit=50{
"success": true,
"data": {
"author": {
"id": "2803301701",
"username": "rmrb",
"display_name": "Example account",
"followers": 1000000,
"joined_at": "2010-01-01T00:00:00Z"
}
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
screen name, username, bio, verified, followers, following, posts_count, location, joined_at
items[] with text, repost, comment and like counts, ext.ip_location, media, cursor
items[] with text, likes, reply count, ext.ip_location, parent_id on replies
hot-search topics with rank, title, heat score, category and badge
Same request lifecycle as every other /v1 platform endpoint. Weibo is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds the weibo route. Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before the read starts.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public page is read live, with retries on 5xx or network errors and a circuit breaker if the source is unhealthy.
Weibo JSON is mapped to the Author, PostList, Post and CommentList archetypes, validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Weibo is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
Public accounts, posts, comments, search results and the hot-search list on weibo.com.
Public pages are read on request and normalized server-side. You never run a Weibo login or session.
Author, PostList, Post, CommentList, AuthorList and SearchResult.
No posting, messaging, follows or private content.
The jobs this API is most often used for.
Chinese social listening and trend tracking
Callers search a topic or an account first, then deepen into posts, comments and replies for the ones that matter. Weibo posts, comments and the hot-search list with the province each was posted from, in the same schema as every other platform, with no Weibo login to manage.
Live misses read the public page on request. Repeat calls hit cache and cost 0 credits.
Common ways teams put this data to work, and the stack each one tends to run.
search for a #topic# over a date window, then comments on the posts that spread.
hot-search snapshots and keyword search to track what China is talking about.
profile for exact counts, profile/posts for recent engagement.
Profile is 1 credit. Posts are 5. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/weibo/profile?id=2803301701" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/weibo/profile/posts?id=2803301701&limit=50" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl