Weibo account posts

A public Weibo account's timeline as a logged-out visitor sees it: its posts with photos or video, newest first, about 20 a page: id, code, link, text, date, source, region, reposts, comments, likes, images, video, topics, the reposted post and the author. Text-only posts are shown to signed-in accounts only. Pass next_cursor back as cursor; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/weibo/v1/user/posts?uid=2803301701" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/weibo/v1/user/posts",
    params={"uid": "2803301701"},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/weibo/v1/user/posts");
url.searchParams.set("uid", "2803301701");

const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).