Weibo user timeline API

Based on the 2026-10-25 specification snapshot

Quick answer

POST /weibo/users/task with author_id, startDate and endDate (all required, dates as YYYY-MM-DD) starts a task that collects a public account's posts in that range. Poll GET /weibo/users/task/{task_id}; once DONE it returns the account ID, a profile object, the timelines and the task metadata. timelines is either a list of posts or an object with data and pagination, and timeline polls take no paging parameters. Data is collected by web crawlers from content publicly published on Weibo.

What teams use it for

  • Follow what the official account of a brand, media outlet or institution published over a period.
  • Keep a dated record of a public account's posts for research.
  • Compare posting activity across several accounts in the same date window.

Endpoints

Base URL: https://api.infominer.io/api/v2. Send your API key in the auth-header request header.

MethodPathWhat it does
POST /weibo/users/task Creates a public account timeline task for an account ID and date range.
GET /weibo/users/task/{task_id} Polls a timeline task; once DONE it returns the profile and the timelines.

Request parameters

POST /weibo/users/task

ParameterInTypeRequiredDefault / allowedDescription
author_id body string Yes Account ID of the public account.
endDate body string Yes End date (YYYY-MM-DD).
startDate body string Yes Start date (YYYY-MM-DD).

GET /weibo/users/task/{task_id}

ParameterInTypeRequiredDefault / allowedDescription
task_id path string Yes Task ID returned when the task was created.

Response fields

DataFieldsEndpoint
Public account timeline id, profile, timelines, task GET /weibo/users/task/{task_id}

Code examples

curl: create the task

curl -X POST https://api.infominer.io/api/v2/weibo/users/task \
  -H "auth-header: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"author_id": "0000000000000001", "startDate": "2026-06-01", "endDate": "2026-06-30"}'

curl: poll the task by ID

curl "https://api.infominer.io/api/v2/weibo/users/task/$TASK_ID" \
  -H "auth-header: YOUR_API_KEY"

Python (requests): create, poll, read

import time
import requests

BASE_URL = "https://api.infominer.io/api/v2"
HEADERS = {"auth-header": "YOUR_API_KEY"}

# 1. Create the task
resp = requests.post(
    f"{BASE_URL}/weibo/users/task",
    headers=HEADERS,
    json={
        "author_id": "0000000000000001",
        "startDate": "2026-06-01",
        "endDate": "2026-06-30",
    },
    timeout=30,
)
resp.raise_for_status()
task = resp.json()

# 2. Poll until the task leaves INIT / RUNNING
for _ in range(120):
    resp = requests.get(
        f"{BASE_URL}/weibo/users/task/{task['id']}",
        headers=HEADERS,
        timeout=30,
    )
    resp.raise_for_status()
    result = resp.json()
    status = result.get("status") or result.get("task", {}).get("status")
    if status not in ("INIT", "RUNNING"):
        break
    time.sleep(15)
else:
    raise SystemExit("task still running; poll it again later")

if status == "FAILED":
    raise SystemExit("task failed")
if status != "DONE":
    print("task ended with status", status, "- results may be incomplete")

# 3. Read the profile and the timeline
print(result.get("profile"))
timelines = result.get("timelines")
rows = timelines.get("data", []) if isinstance(timelines, dict) else (timelines or [])
print(len(rows), "posts")

Sample response

Illustrative data written by hand: accounts are sample_user_n and IDs are obviously fake. Fields follow the 2026-10-25 specification snapshot; the sample shows a subset, and the full list is in the table above.

Task creation response (illustrative data). The snapshot does not enumerate the fields inside profile and timelines, so confirm them with trial data.

{
  "id": "00000000-0000-4000-8000-000000000001",
  "author_id": "0000000000000001",
  "startDate": "2026-06-01",
  "endDate": "2026-06-30",
  "status": "INIT",
  "tm": 1780272000
}

Limits and notes

  • author_id, startDate and endDate are all required.
  • timelines is returned either as a list or as an object with data and pagination.
  • Only content publicly published on Weibo is collected.
  • How far back timelines go and refresh frequency are confirmed per project scope.
Collection: web crawlers collect content publicly published on each platform. Whether this suits your use depends on the purpose and jurisdiction and is for the buyer's legal team to assess; we can provide a description of sources and collection methods.

More Weibo API pages

Request a trial

In the request form below, mention Weibo and tell us the keywords to track (Chinese, or English for a translation subscription), whether you need comments, reposts and repost chains, and the expected volume. We confirm the scope and reply with the arrangements for the trial and API key.

Fill in the form to request a trial. We confirm the scope and reply with trial and integration arrangements.

Fill in the request form

FAQ

Can I collect posts from a private account?
No. Only content publicly published on Weibo is collected.
Does the timeline include comments?
The timeline task collects the account's posts. To collect comments, create a comment task for each post URL with the Weibo comments API.
Is there paging on the timeline result?
The poll takes no paging parameters. timelines is returned either as a list or as an object with data and pagination.
How is the data collected? Is this the official Weibo API?
By web crawlers, from content publicly published on Weibo. LargitData is not affiliated with Weibo and this is not Weibo's own API. Whether this suits your use depends on the purpose and jurisdiction and is for your legal team to assess; we can provide a description of sources and collection methods.