Weibo API
10 endpoints read Weibo: posts, users, comments, trends. From $0.0020 a call. No Weibo login and no cookie; a failed call is free.
One call, as it came back
A recorded call, fields already tidied up: ready for an AI or a spreadsheet.The first 7 rows of a response recorded 2026-10-12 19:03 UTC.
Run it in the Playground · $0.0020{
"code": "ok",
"request_id": "814a139c-cdb8-4a40-ac78-d5eea33f4a49",
"data": {
"items": [
{
"id": "5236052452850013",
"url": "https://weibo.com/6203910512/imMkNQ4Yv",
"type": "image",
"text": "周末的新能源汽车日常，随手记录一下",
"published_at": "2026-10-12T18:01:10.000Z",
"author": {
"id": "6779824410",
"name": "山野咖啡馆",
"avatar_url": "https://tvax1.sinaimg.cn/crop.0.0.512.512.180/E3e34Zyl6RyCChKcvEs7K6EZ.jpg",
"verified": false,
"followers": 2568
},
"metrics": { "likes": 0, "comments": 3, "reposts": 0 },
"images": [
"https://tvax1.sinaimg.cn/large/zhuR7jHU35sRnwVn0Z3jHZz1.jpg",
"https://tvax1.sinaimg.cn/large/OovUGuApFODFZj7FAMuTAB4S.jpg",
// … 2 more
],
"hashtags": null
},
// … 8 more
]
},
"page": {
"next_cursor": "c1.Zaf7tnLyz10UhVmeSCiY-wqUpL2K-Pv9eZq__BRv",
"cursor_expires_at": "2026-10-12T20:03:07.000Z",
"has_more": true,
"returned": 9
},
"warnings": [],
"meta": {
"capability": "weibo.posts.search",
"result_status": "complete",
"fetched_at": "2026-10-12T19:03:07.000Z",
"cached": false,
"replayed": false,
"unavailable": {
"title": "platform",
"lang": "capability",
"author.username": "platform",
"metrics.shares": "platform",
"metrics.favorites": "capability",
"metrics.views": "capability",
"mentions": "capability",
"is_pinned": "capability",
"post_id": "platform",
"parent_id": "platform",
"root_id": "platform"
},
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
}
}
}From a response recorded 2026-10-12 19:03 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.
What you can get
Each row is an endpoint: what it returns and what one call costs.
What people build with it
Ready-made tasks your AI can run on Weibo data. Each is a few calls under a spending cap.
Comments and word of mouth
“What are people praising and complaining about under this post?”
Competitor account monitoring
“What did competitors post this week, and which post took off?”
Keyword search and mentions
“What is being said about this brand or keyword on each platform?”
Ask about Weibo right inside Claude or Cursor
Add the DataXAPI MCP server and the AI finds the Weibo endpoint it needs and calls it; answers link back to the source. You pay for the calls it makes.
https://api.dataxapi.com/mcpStart in three steps
The call shown here is Weibo realtime search. Every other Weibo endpoint is called the same way and answers in the same envelope.
Get a key
Sign in with an emailed code or Google. Free trial, no card needed.
Call it, or let your AI call it
One GET from your code. Or paste this prompt into your agent with your key in it: it sets itself up, then finds and calls these endpoints by itself.
Read the same shape every time
Items are in data.items (one object in data.item), the next page in page.next_cursor, the charge in meta.billing.amount. A failed call is not charged.
curl -G "https://api.dataxapi.com/v1/weibo/posts/search" \ --data-urlencode "query=新能源汽车" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.weibo.posts.search(query="新能源汽车") print(result["data"]["items"])
import { DataXAPI } from "@dataxapi/sdk";
const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.weibo.posts.search({ query: "新能源汽车" });
console.log(result.data.items);dataxapi call weibo.posts.search 'query=新能源汽车'{
"mcpServers": {
"dataxapi": {
"type": "http",
"url": "https://api.dataxapi.com/mcp",
"headers": {
"Authorization": "Bearer ${DATAXAPI_API_KEY}"
}
}
}
}Add this to your MCP client, then ask your agent to call weibo.posts.search.
Edge cases
What the Weibo endpoints do at their edges, and what to check when a call does not return what you expected.
- Page sizes
- A list returns 10 to 100 items a page, depending on the endpoint. 6 of the 8 lists go on to a next page:
page.next_cursor, passed back ascursor, each page a call of its own. The others return one page only. - Fields it cannot give
- 10 of the 10 endpoints cannot fill every field of the object they return. Each endpoint's page lists which, and every answer repeats them in
meta.unavailable: a missing field is never a silent zero. - Snapshots
- Weibo hot search board: a board is a snapshot refreshed every 10 minutes, and
meta.fetched_atsays when it was taken. - The user ID (uid)
- A user is named by the digits after weibo.com/u/ in a profile link.
- Lists cut long posts short
- Search and a user's posts cut a long post short; post detail gives the whole text.
- Likers: the latest batch
weibo.posts.likers.listreturns about the 50 most recent likers, with no further page.- Ads are left out
- Search skips the posts placed as ads, and the hot list skips its ad slot and the entry pinned above it.
- Read and follower counts
- Reads come only on posts that show them; elsewhere the field is null. User search gives no follower count: read the profile.
Questions about the Weibo API
Short answers. The details are on each endpoint's page.
How is the Weibo API priced?
Per call, no subscription. All 10 endpoints cost $0.0020 a call. You are charged when data comes back; a failed call costs nothing.
Do I need a Weibo account or a cookie?
No. One DataXAPI key is all you hold: no Weibo login, no cookie, no device to keep alive. The endpoints return publicly visible data only.
Is the data live?
A call fetches from Weibo at that moment, and meta.fetched_at says when. Weibo hot search board: a board is a snapshot refreshed every 10 minutes. A result is kept for 24 hours, so a retry with the same Idempotency-Key is not charged again.
Is an empty result charged?
A list that comes back empty is charged its price: the search was run. Reading one object that does not exist answers not_found and is free.
What happens when Weibo changes something?
A call that fails is not charged, whatever the reason. An endpoint that is paused answers capability_paused, also free, and GET /v1/catalog/status says what is up right now.
Related
Call Weibo with one key.
Free trial on sign-up: up to 50 calls at $0.0020. No card. No Weibo login, no cookie, no subscription. A failed call is free.