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. 9. 26.Verified working

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

Preview

Try online출시 예정Provider 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이며 서비스 수수료가 포함되어 있습니다.