ApifyWeiboSocial

Weibo realtime hot-search board

apify.weibo.trending.hot_search

Weibo's realtime hot-search board (热搜榜, about 50 entries) with no login — word, rank, heat, label, pinned flag and the search URL per entry

Price: $0.005/resultプロバイダー原価
Success rate: —成功率データはまだありませんLast 30 days · 3 calls
Latency p50: ——
Last verified: 2026/09/26Verified working

POSThttps://toolswitch.dev/v1/tools/apify.weibo.trending.hot_search?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05

Preview

Try onlineProvider docs ↗

Uses platform quota
Synchronous response
Reads public data

パラメータ

the response is the dataset items array directly — no run envelope, no polling. No login and no cookies needed from the caller. The same actor serves apify.weibo.search.posts, .trending.hot_search, .user.posts, .user.profile, .post.detail and .post.comments; `mode` selects which, and a field that belongs to another mode is rejected rather than ignored. Each row carries rank, word, note, heat, label (热/新/沸…), is_pinned and the s.weibo.com search url; pinned entries carry rank and heat null

パラメータ	型	必須	説明	例
クエリパラメータ
`memory`	整数	任意	MB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size	`1024`
`timeout`	整数	任意	run timeout in seconds. treg's key requires 90 so the run and its rows arrive before any wait gives up; a larger pull should use your own key and the async web.scrape.job.* pair above	`90`
`maxItems`	整数	任意	optional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit	`50`
`maxTotalChargeUsd`	数値	任意	the spend cap Apify enforces on every event this run bills, in dollars. treg's key requires it, above 0 and at most 1, and holds it for the call	`0.5`

クエリパラメータ
memory整数任意
MB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size
例：1024
timeout整数任意
run timeout in seconds. treg's key requires 90 so the run and its rows arrive before any wait gives up; a larger pull should use your own key and the async web.scrape.job.* pair above
例：90
maxItems整数任意
optional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit
例：50
maxTotalChargeUsd数値任意
the spend cap Apify enforces on every event this run bills, in dollars. treg's key requires it, above 0 and at most 1, and holds it for the call
例：0.5

コード例

$TOOLSWITCH_KEY をコンソールで作成したキーに置き換えてください。

Preview

curl -X POST 'https://toolswitch.dev/v1/tools/apify.weibo.trending.hot_search?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05' \
  -H "X-Toolswitch-Key: $TOOLSWITCH_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"mode":"hot_search","max_items":1}'

import os
import json
import requests

response = requests.request(
    "POST",
    "https://toolswitch.dev/v1/tools/apify.weibo.trending.hot_search?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05",
    headers={"X-Toolswitch-Key": os.environ["TOOLSWITCH_KEY"]},
    json=json.loads("{\"mode\":\"hot_search\",\"max_items\":1}"),
)
response.raise_for_status()
print(response.text)

const response = await fetch("https://toolswitch.dev/v1/tools/apify.weibo.trending.hot_search?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05", {
  method: "POST",
  headers: {
    "X-Toolswitch-Key": process.env.TOOLSWITCH_KEY ?? "",
    "Content-Type": "application/json",
  },
  body: JSON.stringify(JSON.parse("{\"mode\":\"hot_search\",\"max_items\":1}")),
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
console.log(await response.text());

このゲートウェイ API はプレビュー版です。URL や認証方式は変更される場合があります。パラメータはサンプルデータです。呼び出し料金は $0.005/result です。サービス料を含みます。