ApifyWeiboSocial

Get a Weibo post by id

apify.weibo.post.detail

One or more Weibo posts by id, short code or URL with no login — FULL long text (search and timeline rows truncate long posts), counts including reads, images, video and topics

Price
$0.005/resultAt provider cost
Success rate
—No success-rate data yetLast 30 days · 0 calls
Latency p50
——
Last verified
Sep 26, 2026Verified working
POSThttps://toolswitch.dev/v1/tools/apify.weibo.post.detail?memory=1024&timeout=90&maxItems=1&maxTotalChargeUsd=0.05Preview
  • Uses platform quota
  • Synchronous response
  • Reads public data

Parameters

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 the full text

ParameterTypeRequiredDescriptionExample
Query parameters
memoryintegerOptionalMB of run memory. treg's key requires 1024, which fixes the actor-start charge; your own key may set any size1024
timeoutintegerOptionalrun 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
maxItemsintegerOptionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit50
maxTotalChargeUsdnumberOptionalthe 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
  • Query parameters
  • memoryintegerOptional

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

    Example: 1024

  • timeoutintegerOptional

    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

    Example: 90

  • maxItemsintegerOptional

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

    Example: 50

  • maxTotalChargeUsdnumberOptional

    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

    Example: 0.5

Code samples

Replace $TOOLSWITCH_KEY with the key you created in the console.

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

This gateway API is in preview; its URL and authentication may change. The example parameters are sample data. Calls are billed at $0.005/result, including the service fee.