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

Parâmetro	Tipo	Obrigatório	Descrição	Exemplo
Parâmetros de consulta
`memory`	inteiro	Opcional	MB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size	`1024`
`timeout`	inteiro	Opcional	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`	inteiro	Opcional	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`	número	Opcional	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`

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

import os
import json
import requests

response = requests.request(
    "POST",
    "https://toolswitch.dev/v1/tools/apify.weibo.user.posts?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05",
    headers={"X-Toolswitch-Key": os.environ["TOOLSWITCH_KEY"]},
    json=json.loads("{\"mode\":\"timeline\",\"users\":[\"2803301701\"],\"max_items\":1}"),
)
response.raise_for_status()
print(response.text)

const response = await fetch("https://toolswitch.dev/v1/tools/apify.weibo.user.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\":\"timeline\",\"users\":[\"2803301701\"],\"max_items\":1}")),
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
console.log(await response.text());

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.