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/resultAt list price
Success rate
—No success-rate data yetNo success-rate data yet
Latency p50
——
Last verified
Sep 26, 2026Verified working
POSThttps://toolswitch.dev/v1/tools/apify.weibo.trending.hot_search?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05Beta
  • Uses platform quota
  • Synchronous response
  • Reads public data

Parameters

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

ParameterTypeRequiredDescriptionExample
Query parameters
memoryintegerOptionalMB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size1024
timeoutintegerOptionalrun 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 above90
maxItemsintegerOptionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit50
maxTotalChargeUsdnumberOptionalthe 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 call0.5
Request body (JSON)
modestringRequiredmust be `hot_search` for this entry — it selects the modehot_search
max_itemsintegerOptionalcaps the whole board (it holds about 50 entries); default 5050
proxyUrlsarray[string]Optionalleave empty to use the residential proxy included in the run price; or pass your own gateway URLs (http://user:pass@host:port)
  • Query parameters
  • memoryintegerOptional

    MB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size

    Example: 1024

  • timeoutintegerOptional

    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

    Example: 90

  • maxItemsintegerOptional

    optional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit

    Example: 50

  • maxTotalChargeUsdnumberOptional

    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

    Example: 0.5

  • Request body (JSON)
  • modestringRequired

    must be `hot_search` for this entry — it selects the mode

    Example: hot_search

  • max_itemsintegerOptional

    caps the whole board (it holds about 50 entries); default 50

    Example: 50

  • proxyUrlsarray[string]Optional

    leave empty to use the residential proxy included in the run price; or pass your own gateway URLs (http://user:pass@host:port)

Code samples

Replace $TOOLSWITCH_KEY with the key you created in the console.

Beta
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}'

This gateway API is in beta; its URL and authentication may change. The example parameters are sample data. Calls are billed at $0.005/result, including the service fee.