ApifyWeiboSocial

List a Weibo user's recent posts

apify.weibo.user.posts

A Weibo user's timeline, newest first, with no login — about 1,000 posts deep per user; same post fields as search

Price
$0.005/resultプロバイダー原価
Success rate
—成功率データはまだありませんLast 30 days · 0 calls
Latency p50
——
Last verified
2026/09/26Verified working
POSThttps://toolswitch.dev/v1/tools/apify.weibo.user.posts?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05Preview
Try online近日公開Provider docs ↗
  • Uses platform quota
  • Synchronous response
  • Reads public data

パラメータ

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 is a post (same fields as apify.weibo.search.posts) with source_user set to the requested user

パラメータ型必須説明例
クエリパラメータ
memory整数任意MB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size1024
timeout整数任意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 above90
maxItems整数任意optional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit50
maxTotalChargeUsd数値任意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 call0.5
  • クエリパラメータ
  • memory整数任意

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

    例:1024

  • timeout整数任意

    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整数任意

    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数値任意

    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

コード例

$TOOLSWITCH_KEY をコンソールで作成したキーに置き換えてください。

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

このゲートウェイ API はプレビュー版です。URL や認証方式は変更される場合があります。 パラメータはサンプルデータです。 呼び出し料金は $0.005/result です。サービス料を含みます。