Weibo hot search board (backup) API
The backup of the Weibo hot search board, to call when the original fails upstream: the same parameters and result, at a higher price. About 50 items a call, 51 at most; $0.0300 per call. Errors and timeouts are not charged; an empty result is charged $0.0300.
Try it
Change a value and the request on the right follows.Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 3 calls.
curl "https://api.dataxapi.com/v1/weibo/backup/trends/list" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
"code": "ok",
"request_id": "5e45539d-5b83-44a8-8294-d30c058b98a9",
"data": {
"items": [
{ "name": "周末露营怎么玩", "rank": 1, "heat": 1179776 },
// … 49 more
]
},
"page": {
"next_cursor": null,
"cursor_expires_at": null,
"has_more": false,
"returned": 50
},
"warnings": [],
"meta": {
"capability": "weibo.backup.trends.list",
"result_status": "complete",
"fetched_at": "2026-10-29T09:44:31.000Z",
"cached": false,
"replayed": false,
"unavailable": { "id": "platform" },
"billing": {
"amount": "0.03",
"currency": "USD",
"balance_after": "9.97"
}
}
}From a response recorded 2026-10-29 09:44 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.
Size as sent: 3.8 KB in the standard view (3.8 KB compact, 3.8 KB full).
{
"code": "ok",
"request_id": "617f947f-ae5d-4fd8-a2ee-b7ab803bcf96",
"data": { "items": [] },
"page": {
"next_cursor": null,
"cursor_expires_at": null,
"has_more": false,
"returned": 0
},
"warnings": [],
"meta": {
"capability": "weibo.backup.trends.list",
"result_status": "empty",
"fetched_at": "2026-10-29T09:44:31.000Z",
"cached": false,
"replayed": false,
"unavailable": { "id": "platform" },
"billing": {
"amount": "0.03",
"currency": "USD",
"balance_after": "9.97"
}
}
}From a recording of 2026-10-29 09:44 UTC, edited by hand to show this case. The request ID and balance are made up.
Size as sent: 422 B in the standard view (422 B compact, 422 B full).
curl "https://api.dataxapi.com/v1/weibo/backup/trends/list" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
# pip install dataxapi from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.weibo.backup.trends.list() print(result["data"]["items"])
// npm i @dataxapi/sdk import { DataXAPI } from "@dataxapi/sdk"; const dx = new DataXAPI(); // reads DATAXAPI_API_KEY const result = await dx.weibo.backup.trends.list(); console.log(result.data.items);
dataxapi call weibo.backup.trends.list
{
"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.backup.trends.list.
Parameters
Which list: hot searches is the only one. Values: hot_search (default). Example: hot_search.
How much of each item to return. All three cost the same. Values: compact, standard (default), full.
Return only these fields. Each by its path, such as author.name.
Known limits
- About 50 items a page, 51 at most. The page size is the platform's;
limitis not accepted. - Everything comes in one page; no cursor is issued.
- Answers come from a shared snapshot refreshed every 10 minutes;
meta.cachedsays so andmeta.fetched_atis when it was taken. - 1 field of the object is not available from this endpoint
Returned fields
data.items is a list of trend objects. Stable: fields are only ever added.
The platform's ID for the entry
Name of the entry
Position on the board, from 1; a pinned entry has none
The platform's heat score
Which numbers of this item are approximate or lower bounds; absent when all are exact
Path of the field, such as metrics.views
Show all 7 fields →
Approximate, or a lower boundapproximatelower_bound
Typical size of one item: compact 70 B, standard 70 B, full 70 B (measured on the response recorded 2026-10-29 09:44 UTC).
What this endpoint cannot give
idThe platform has noneWhen you are charged
X-Max-Price to refuse anything above your own limit)Prices as read 2026-11-02 11:50 UTC, under price book 8, in effect since 2026-11-02 11:46 UTC; the Playground reads the price in force before a run.
Errors
What this endpoint can answer with; codes all endpoints share are on the full list.
This is a backup version: the same parameters and fields as the original, from another source, at its own price. The original is the one to call first: Weibo hot search board API
invalid_paramsA parameter is invalidRetry: After a fixNoinsufficient_balanceThe balance is too lowRetry: After a fixNoupstream_failedNo result came from the data source this time. Retry later; if the same item keeps failing, it most likely cannot be retrieved (deleted or restricted, say)Retry: YesNotimeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNoQuestions
How much does the Weibo hot search board (backup) API cost?
$0.0300 per call. The most one call can cost is $0.0300.
When am I not charged?
Errors and timeouts are not charged; an empty result is charged $0.0300.
How many items does one call return, and how do I get the next page?
About 50 items a page, 51 at most. The page size is the platform's; limit is not accepted. Everything comes in one page; no cursor is issued.
30-day availability
100% of the time over the last 16 days (since 2026-10-17, when the record began), this endpoint was serving calls: at least one of its routes was taking them, so it was neither paused nor down.
It is not a success rate: how single calls went is not in it, and a failed call is not charged either way.
Every endpoint's state now, and each incident with whether anyone was charged: the status page →
The same thing on other platforms
All 11 Weibo endpoints
Use it in your AI
Copy this prompt
Your API key is built in, so there is nothing to configure.
No account yet? Sign-up takes an email and no card, and a failed call is never charged.
Paste it into your agent
It reads the page the prompt points to and connects itself.
Now ask something
Use one of these, or your own words.
Prefer to set it up by hand?
dataxapi setupgives the agents on your machine (Claude Code, Codex, Cursor) the DataXAPI MCP server and the base skill. The key is read from DATAXAPI_API_KEY; none is written into a file.MCP server: https://api.dataxapi.com/mcp. The entry for your client is under MCP in the request examples of this page; then ask your agent to call weibo.backup.trends.list.Other clients →Show the text
Use the DataXAPI endpoint weibo.backup.trends.list (Weibo hot search board (backup)). The backup of the Weibo hot search board, to call when the original fails upstream: the same parameters and result, at a higher price. Call GET https://api.dataxapi.com/v1/weibo/backup/trends/list with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code. Parameters: - board: Which list: hot searches is the only one. Values: hot_search (default). Example: hot_search. - view: How much of each item to return. All three cost the same. Values: compact, standard (default), full. - fields: Return only these fields. Each by its path, such as author.name. Price: $0.0300 per call. Errors and timeouts are not charged; an empty result is charged $0.0300. The answer is JSON: data.items holds trend; meta.billing.amount is what this call was charged. Example: curl "https://api.dataxapi.com/v1/weibo/backup/trends/list" \ -H "Authorization: Bearer $DATAXAPI_API_KEY" Full reference in Markdown: https://dataxapi.com/apis/weibo/backup/trends/list.md
Names and identifiers
- In Chinese
- 微博热搜榜(备用版)API
- Endpoint ID
weibo.backup.trends.list- Endpoint
GET /v1/weibo/backup/trends/list
Start with one key.
226 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.