ApifyWeiboSocial

List a Weibo post's comments

apify.weibo.post.comments

Comments on Weibo posts with no login, hot-first or newest-first, optionally with each comment's reply thread — text, likes, reply count, floor, IP region and commenter per row

Price
$0.005/resultZum Anbieterpreis
Success rate
—Noch keine ErfolgsratendatenLast 30 days · 0 calls
Latency p50
——
Last verified
26.09.2026Verified working
POSThttps://toolswitch.dev/v1/tools/apify.weibo.post.comments?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 comment_id, post_mid, root_id, is_reply, reply_to_id, floor_number, created_at, text/text_raw, source (IP region), like_count, reply_count, liked_by_author and the commenter (user_id, screen name, verification). Replies also answer weibo.comment.replies

ParameterTypErforderlichBeschreibungBeispiel
Abfrageparameter
memoryGanzzahlOptionalMB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size1024
timeoutGanzzahlOptionalrun 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
maxItemsGanzzahlOptionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit50
maxTotalChargeUsdZahlOptionalthe 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
  • Abfrageparameter
  • memoryGanzzahlOptional

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

    Beispiel: 1024

  • timeoutGanzzahlOptional

    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

    Beispiel: 90

  • maxItemsGanzzahlOptional

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

    Beispiel: 50

  • maxTotalChargeUsdZahlOptional

    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

    Beispiel: 0.5

Codebeispiele

Ersetze $TOOLSWITCH_KEY durch den in der Konsole erstellten Schlüssel.

Preview
curl -X POST 'https://toolswitch.dev/v1/tools/apify.weibo.post.comments?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05' \
  -H "X-Toolswitch-Key: $TOOLSWITCH_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"mode":"comments","post_ids":["https://weibo.com/2803301701/Rjuwfpy8d"],"max_items":1}'

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.