Weibo Hot Search Scraper

Fetch the Weibo realtime hot search list (top ~100 trends) via the upstream Chinese social data API. Built for marketing monitoring, trend research, and public sentiment scraping.

One run = one upstream request. Pick a preset (realtime_hot / entertainment / social / technology / life) or pass a raw containerid, and a page number (1..5). Each page returns ~20 trends; the full hot list is ~100 across pages 1..5.

• Actor ID: TF51J1LwZ2AayIXzd
• Build: 0.1.6
• Source: A hosted Chinese social data API provider (Weibo endpoints)

What it does

Input	Output
preset=realtime_hot + page=1 (defaults)	~20 trend items with rank, post_id, mid, text, source, reposts/comments/attitudes counts, and a flat user profile. Raw upstream payload preserved in rawData.

Quick start

{
  "preset": "realtime_hot",
  "page": 1
}

Output dataset has one item per trend:

{
  "rank": 1,
  "post_id": "5328347665010605",
  "mid": "5328347665010605",
  "created_at": "Wed Aug 05 00:22:22 +0800 2026",
  "text": "现在拍戏都这么拼吗 [允悲] 女演员工伤 偷胯婆的微博视频",
  "text_length": 57,
  "source": "iPhone 17 Pro Max",
  "pic_ids": [],
  "reposts_count": 142,
  "comments_count": 523,
  "attitudes_count": 1820,
  "user": {
    "user_id": 7491687377,
    "screen_name": "偷胯婆",
    "verified": true,
    "verified_type": 0,
    "followers_count": "2.3万"
  },
  "rawData": { /* full upstream status object */ }
}

Input fields

Field	Required	Default	Notes
preset	no	realtime_hot	One of realtime_hot, entertainment, social, technology, life.
containerid	no	(preset)	Raw Weibo containerid for custom lists. Overrides preset when both provided.
page	no	1	Page number (1..5). Each page returns ~20 trends.

5 default presets cover the official Weibo top lists. Per our internal SOP §40 — every value the upstream supports must be exposed — all 5 are wired here. To use a custom containerid, copy it from any public Weibo endpoint response or pass your own string.

Pricing

Free users are limited to 5 runs per day. Paid users (APIFY_USER_IS_PAYING=1) have unlimited runs. The Actor itself adds no markup — you pay the upstream provider per request plus the standard Apify compute unit cost.

Output

The Actor pushes one item per trend to the default dataset and writes a SUMMARY record to the default key-value store with run details (preset, container id, page, total from upstream, free-run counter, etc.).

Use it together with the other Weibo Actors

This Actor is the step ① entry point of the 3-Actor Weibo MVP-2 set. Use it together with:

Where in the pipeline	Actor	Console	Use it to
before / step ①	Weibo Hot Search Scraper (you are here)	(step ① — entry point)	step ① — fetch the realtime hot list, get post_id and screen_name of each trend
after / step ②	Weibo Keyword Search Scraper	Console	step ② — search posts by keyword with 7 type filters and 4 time scopes
after / step ③	Weibo Post Detail Scraper	Console	step ③ — pull full post text + up to ~150 comments for one post_id

You are here: Weibo Hot Search Scraper — run this on its own for the upstream use case described above.

Why this Actor exists

Apify has ~50,000 Actors and almost zero Weibo scrapers. This Actor is the first of a planned Weibo MVP-2 set (5 Actors covering hot search, keyword search, user profile, post detail + comments, and channel feed) that targets the gap.

Source & credits

Data source: a hosted Chinese social data API provider (Weibo endpoints). The provider charges per upstream request; this Actor adds no markup.

License

MIT