Weibo Public Data API | SandBase
Read public Weibo hot search, posts, and user profiles with one REST API. No Weibo OAuth app, no SDK — one SandBase key, built for agent workflows.

Weibo is where Chinese public opinion, celebrity news, and trending topics surface first, which makes its hot-search board, post streams, and profile data valuable for social listening, market research, and agent workflows. Getting at it programmatically usually means reverse-engineering a mobile app, rotating cookies, and rebuilding a scraper every time the site changes.
The SandBase Weibo public data API removes that setup tax. It reads public Weibo hot search, search results, posts, and user profiles through plain REST endpoints — one SandBase API key, no Weibo login and no SDK. The endpoint API reference is the source of truth for each parameter and for the response envelope; the business-payload field names shown below are an illustrative shape, not a guaranteed schema, so confirm them against a live response for the endpoint you call.
This is not Sina Weibo’s official open platform. Use Weibo’s official APIs when you need authenticated member actions or a licensed data agreement. Use SandBase when your workflow needs public, read-only data for research and monitoring. Ready to try it? Get a SandBase API key and browse the Weibo endpoints.
Key takeaway
- One API reads public Weibo hot search, search results, posts, comments, and user profiles.
- The Model API endpoints in this guide are called with
POST /v1/api/weibo/<path>— pass only that endpoint’s params, no SDK, oneSANDBASE_API_KEY.- Endpoints key off natural identifiers: a
uidfor users, astatus_id/mid/idfor a post, or aquery/keywordfor search.- It returns public, read-only data only. There is no posting, no login on your side, and no private or follower-only data; authenticate with a SandBase API key.
Current scope: one known account request
The retained cover is conceptual artwork. Its sample names, counts and hot-search headlines are not API measurements, current rankings or model benchmarks.
The 2026-11-08 repair checked free inspect and public references for user-info and user-posts. It made no paid business call. Broader capability descriptions and screenshots below are retained from the earlier hub, published 2026-09-27 and updated 2026-10-01; hot-search, search, detail and comment execution were not revalidated.
Choose one task: read a profile with exactly one of uid or custom, or read one ordinary timeline page using numeric-string uid, page: 1, feature: 0, with no since_id. The latter may include reposts; it is not the original-only endpoint. The account tutorial provides a tested single-request helper and the existing-key, connected-agent and new-project setup paths.
Both selected inspections show $0.001 base price and eligibility for the organization’s shared 100 daily calls across eligible APIs, reset 00:00 UTC. Remaining allowance and actual charges were not checked. One selected request is not a free-success promise. Extra pages and follow-up endpoints require their own validation and budget.
Which Weibo API do you need?
| Your need | Choose | Why |
|---|---|---|
| Post, act as a member, or use account-authorized data | Weibo’s official platform | Member and account operations run through Weibo directly. |
| Read public hot search, posts, or profiles | SandBase Weibo public-data API | Plain REST, one SandBase key, structured JSON for read-only workflows. |
| Private or follower-only data | Neither public workflow | That data is out of scope for this public-data guide. |
What you can get from the Weibo API
The catalog spans several surfaces (an app surface, a web surface, and a newer web-v2 surface). Grouped by job:
- Hot search & trends — the realtime hot-search board and trend rankings.
- Search — realtime search, topic search, and advanced search by keyword.
- Posts — status detail, comments, reposts, and likes for a post.
- Users — public profile info, timelines, videos, and articles by
uid.
Check each endpoint’s live API reference for the exact surface and parameters before you build; availability differs by endpoint.
Historical Weibo catalog overview. Retained from the prior article; this screenshot is not a new business run or an endpoint revalidation.
What Weibo provides vs. what SandBase adds
Public data comes from Weibo; SandBase does not own or operate Weibo. Shared authentication simplifies access, but each endpoint still needs its own input, business-response and availability checks. One envelope does not prove a hot-search-to-profile chain works today. The current first-request path stops after either a profile or one timeline page.
Quick start: one known profile
Use the Model API POST route, not a catalog GET path. Configure SANDBASE_API_KEY locally. This bounded cURL sends only uid; do not also send custom. It prints the response and does not validate business success by itself. For checked Python, use the account tutorial. For setup, give your agent SKILL.md and quickstart.md with one chosen task.
curl --fail-with-body --connect-timeout 10 --max-time 90 \
-X POST https://api.sandbase.ai/v1/api/weibo/web-v2/user-info \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"uid":"1222135407"}'Validate completed status and an object at outputs[0].data. A profile reference contains a user object; the tutorial also requires it to be nonempty as a local completeness guard. For the alternative posts task, require integer ok: 1, a data object and data.list array of objects. Explicit booleans, missing structures and a saved invalid-UID example with outer code: 200 must not be accepted as success. Keep optional missing counts unknown instead of substituting zero.
The original profile README’s response sample used both identifiers; it remains historical reference evidence, not a new one-identifier execution. The original Python hot-search snippet is preserved in the historical code archive. Its unchecked empty-list fallback is not current guidance. The following original hot-search JSON is retained unchanged as historical illustrative material, not the response from the profile request above:
{
"id": "cb805c67-4817-4926-9639-24a15e694cc9",
"status": "completed",
"model": "weibo/web-v2/hot-search",
"outputs": [
{
"data": {
"realtime": [
{ "rank": 0, "word": "…", "note": "…", "num": 1172365 }
]
}
}
]
}Any status other than completed must stop this first-request workflow. Do not depend on error-body details or fall back to empty data. Each endpoint needs its own business validation, even when the envelope matches.
Historical hot-search reference. Its old generated cURL includes a model field; do not copy it into the current endpoint-parameter-only request. This screenshot is not a new business run or endpoint revalidation.
Capability map
The table retains historical navigation from the prior hub; only user-info and user-posts were checked in this repair. Its other endpoint inputs and current execution remain unverified.
| Capability cluster | Representative endpoint | Typical use |
|---|---|---|
| Hot search | weibo/web-v2/hot-search | Trending-topic monitoring |
| Realtime search | weibo/web-v2/realtime-search | Topic and keyword discovery |
| User profile | weibo/web-v2/user-basic-info | Public account signals by uid |
| Post detail | weibo/app/status-detail | Read a single post by status_id |
| Post comments | weibo/app/status-comments | Engagement and sentiment inputs |
Paging differs by endpoint — several endpoints accept a request parameter such as a page or cursor value. Read each endpoint’s schema.
Historical user-basic-info parameter reference. Retained from the prior article; this screenshot is not a new business run or an endpoint revalidation.
Before chaining calls
A trend-to-author workflow is a possible research design, not a result established by the current repair. Check each endpoint’s inputs, business shape, identifier mapping, availability and cost before adding it. Validate status and payload separately for every request, rather than checking once for the whole chain.
For account research, the original-posts schema says an initial since_id comes from user-posts, while its README discusses subsequent paging and omits the token in cURL. The dated tutorial experiment succeeded without it in 2026-10-01, but does not resolve today’s conflict. Do not guess a starting cursor or quietly add a preceding call. Start with the ordinary user-posts first page if that meets your task, and keep reposts distinct from original content.
Common use cases
Weibo hot-search API for trend monitoring
Poll weibo/web-v2/hot-search on a schedule to track the realtime board — each item carries a ranked keyword and a popularity number. Input: none. Output: a ranked list of trending topics. Endpoint: hot-search. For a full workflow, see how to monitor Weibo hot search.
Weibo search API for topic discovery
Run weibo/web-v2/realtime-search with a query to surface posts around a topic. Input: a query. Output: matching posts. Endpoint: realtime-search.
Weibo profile API for account research
Read a public profile with weibo/web-v2/user-info, choosing exactly one of uid or custom. Read numeric followers_count when present; keep missing counts unknown. The historical lighter basic-info observation did not include a numeric follower count, and that endpoint was not revalidated in this repair. For a checked profile/posts first request and separately dated original-post research, see how to research a Weibo account’s posts.
What to retain after the first read
Save the selected endpoint, input identifiers and observation time alongside the returned payload. Keep numeric zero, explicit false, null and missing fields distinct. A profile follower count is not a reach estimate; a timeline page is not the account’s complete history. Returned media URLs are references, not verified downloads.
Use the first response to decide whether your actual research question is answerable. A profile can help confirm the intended public account. A posts page can show sample records and available counts. Neither alone establishes a complete campaign ranking, original-only collection or sponsored-content classification. Expand only after reviewing the unknowns and the next request’s budget.
Limitations and boundaries
- Public, read-only data only. No posting, following, or private/follower-only data.
- Rate and volume. Stop on errors, inspect the cause and budget before resending; the first-request examples do not retry automatically.
- Parameters and shapes follow the upstream surface. Identifiers vary (
uid,status_id/mid/id,query/keyword); paging is a per-endpoint request parameter. Inspect a real response and read the schema first. - Verify endpoints against the live reference. Availability and fields can change; confirm before building on a specific endpoint.
- This is not an official Weibo partnership. SandBase provides uniform access to public data; respect Weibo’s terms and applicable rules for your use case.
FAQ
Do I need a Weibo developer app or login?
No. You authenticate to SandBase with your SANDBASE_API_KEY. These read endpoints do not require a Weibo account or OAuth on your side.
What identifies a user or post?
Natural identifiers: a uid for users and a status_id/mid/id for a post. Search takes a query or keyword.
How does pagination work? It depends on the endpoint — several accept a per-endpoint page or cursor request parameter. Read each endpoint’s schema.
Can I read private or follower-only data? No. The API returns public data only. Private accounts and follower-only content are out of scope.
Start with one known account
Configure your key, choose profile or one ordinary posts page, and validate the result before expanding. For historical hot-search guidance, use its dedicated tutorial. When you are ready:
Found this useful? Share it