Xiaohongshu Keyword Search Scraper
Pricing
$0.10 / actor start
🔍 小红书关键词搜索爬虫 | Xiaohongshu Keyword Search 按关键词搜索小红书笔记,支持 3 种核心筛选:排序方式(sort_order)、笔记类型(note_type)、发布时间(publish_time)。 自动翻页 + 去重,返回标准化数据集 + 原文 payload。
estimatedUpstreamCostUsd SUMMARY field removed: was a 1:1 mirror of upstream pricing.$0.01 per request comment removed from src/main.js.page input (1-10) for explicit paginationsearchId and searchSessionId inputs (required for page >= 2)nextSearchId, nextSearchSessionId, actualRequests, actualPageshasMore=false breakmaxItems input (cap matched real upstream capacity of ~20 notes per page)MAX_PAGES_PER_RUN constant (Skill §17.4 explicitly relaxed for this Actor)MAX_ITEMS_HARD_CAP constant (no longer needed without maxItems)sortType input (6 enum values, default general)noteType input (4 enum values, default 不限)timeFilter input (4 enum values, default 不限)enumTitles schema validation: switch to Array<string> matching enum ordersearch_id and search_session_id paginationenvironmentVariables (skill §4.1 owner-self-use pattern): TIKHUB_API_KEY and TIKHUB_BASE_URL are now baked into the Actor build. Users no longer need to add the TIKHUB_API_KEY secret in the Apify Console before their first run. The Actor description's "no setup or API key required" promise is now actually true at runtime.TIKHUB_BASE_URL default: explicit inline value https://api.tikhub.io (was previously relying on the code-level DEFAULT_BASE_URL fallback). Inline mode ships the base URL alongside the key.src/tikhub_client.js → src/upstream_client.js; class TikHubClient → UpstreamClient; actor.json env keys TIKHUB_API_KEY / TIKHUB_BASE_URL → UPSTREAM_API_KEY / UPSTREAM_BASE_URL. Inline raw values unchanged. Per our internal SOP §100 (no upstream brand name in user-facing surfaces), the visible name "TikHub" no longer appears in actor.json / main.js / client class name. Existing deployments transition seamlessly because this Actor uses inline keys, not Secret refs.