
List a Weibo post's comments
From Apify, through Joshu Data Bodega.
Part of Weibo post comments.
- Price
- $0.0055 per call$5.50 per 1,000 calls
No calls measured in the last 30 days.
Prices include the router's 10% markup and are paid from the usage wallet. Checked on November 11, 2026.
Inputs
modestring, requiredmust be `comments` for this entry — it selects the mode
memoryinteger: 1024, optionalMB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size
timeoutinteger: 90, optionalrun 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
maxItemsinteger, optionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit
post_idsstring, requiredone per entry: numeric mid, mblogid short code, or post URL
max_itemsinteger, optionalcomments per post, 1-10000, replies included; default 50
proxyUrlsstring, optionalleave empty to use the residential proxy included in the run price; or pass your own gateway URLs (http://user:pass@host:port)
comment_sortstring, optionalhot (default, most-liked first) | time (newest first)
include_repliesboolean, optionalalso walk each comment's reply thread; replies come back as rows with is_reply true and root_id linking them to their comment, and bill as comments. Default false
maxTotalChargeUsdnumber, optionalthe 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
Call it
curl https://hello.joshu.me/api/router/call \
-H "Authorization: Bearer $JOSHU_ROUTER_KEY" \
-H "Content-Type: application/json" \
-d '{
"endpoint": "apify.weibo.post.comments",
"params": {
"mode": "comments",
"memory": 1024,
"timeout": 90,
"maxItems": 1,
"post_ids": [
"https://weibo.com/1234567890/abc123"
],
"max_items": 1,
"maxTotalChargeUsd": 0.05
}
}'