Search Weibo posts by keyword
apify.weibo.search.postsSearch Weibo posts by keyword or #topic# with no login — relevance (top, up to ~2,000 posts per keyword) or newest-first (latest, walks back in time without a depth ceiling), optionally within a Beijing-time date range; text, counts, images, video, topics and author per post
- Price
- $0.005/resultZum Anbieterpreis
- Success rate
- —Noch keine ErfolgsratendatenLast 30 days · 4 calls
- Latency p50
- ——
- Last verified
- 26.09.2026Verified working
POSThttps://toolswitch.dev/v1/tools/apify.weibo.search.posts?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05Preview- Uses platform quota
- Synchronous response
- Reads public data
Parameter
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 mid, mblogid, url, created_at, text/text_raw, reposts/comments/attitudes counts, image_urls, video fields, topics, repost linkage and the author (user_id, screen name, verification, followers), plus source_keyword
| Parameter | Typ | Erforderlich | Beschreibung | Beispiel |
|---|---|---|---|---|
| Abfrageparameter | ||||
memory | Ganzzahl | Optional | MB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size | 1024 |
timeout | Ganzzahl | Optional | 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 | Ganzzahl | Optional | 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 | Zahl | Optional | 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 |
- Abfrageparameter
memoryGanzzahlOptionalMB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size
Beispiel:
1024timeoutGanzzahlOptionalrun 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
Beispiel:
90maxItemsGanzzahlOptionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit
Beispiel:
50maxTotalChargeUsdZahlOptionalthe 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
Beispiel:
0.5
Codebeispiele
Ersetze $TOOLSWITCH_KEY durch den in der Konsole erstellten Schlüssel.
curl -X POST 'https://toolswitch.dev/v1/tools/apify.weibo.search.posts?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05' \
-H "X-Toolswitch-Key: $TOOLSWITCH_KEY" \
-H "Content-Type: application/json" \
--data-raw '{"mode":"search","keywords":["咖啡"],"max_items":1}'import os
import json
import requests
response = requests.request(
"POST",
"https://toolswitch.dev/v1/tools/apify.weibo.search.posts?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05",
headers={"X-Toolswitch-Key": os.environ["TOOLSWITCH_KEY"]},
json=json.loads("{\"mode\":\"search\",\"keywords\":[\"咖啡\"],\"max_items\":1}"),
)
response.raise_for_status()
print(response.text)const response = await fetch("https://toolswitch.dev/v1/tools/apify.weibo.search.posts?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\":\"search\",\"keywords\":[\"咖啡\"],\"max_items\":1}")),
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
console.log(await response.text());Diese Gateway-API ist eine Vorschauversion; URL und Authentifizierung können sich ändern. Die Beispielparameter sind Musterdaten. Aufrufe werden mit $0.005/result einschließlich Servicegebühr abgerechnet.