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/resultPelo preço do provedor
Success rate
—Ainda não há dados da taxa de sucessoLast 30 days · 0 calls
Latency p50
——
Last verified
26 de set. de 2026Verified working
POSThttps://toolswitch.dev/v1/tools/apify.weibo.post.comments?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05Preview
Try onlineEm breveProvider docs ↗
  • Uses platform quota
  • Synchronous response
  • Reads public data

Parâmetros

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

ParâmetroTipoObrigatórioDescriçãoExemplo
Parâmetros de consulta
memoryinteiroOpcionalMB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size1024
timeoutinteiroOpcionalrun 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
maxItemsinteiroOpcionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit50
maxTotalChargeUsdnúmeroOpcionalthe 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
  • Parâmetros de consulta
  • memoryinteiroOpcional

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

    Exemplo: 1024

  • timeoutinteiroOpcional

    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

    Exemplo: 90

  • maxItemsinteiroOpcional

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

    Exemplo: 50

  • maxTotalChargeUsdnúmeroOpcional

    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

    Exemplo: 0.5

Exemplos de código

Substitua $TOOLSWITCH_KEY pela chave criada no console.

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}'

Esta API de gateway está em prévia; a URL e a autenticação podem mudar. Os parâmetros do exemplo são dados de amostra. As chamadas são cobradas a $0.005/result, incluindo a taxa de serviço.