Can I translate any Weibo post on demand?

No. Only posts covered by your subscribed keywords are translated. The query endpoints read translated records that already exist.

Is the translation done by people?

No. It is machine translation. Translated comments carry post_id and translated reposts carry parent_id, so they link back to the posts they belong to.

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.

Weibo English translation API

Based on the 2026-10-25 specification snapshot

Quick answer

For teams that do not read Chinese, Weibo data is available with English machine translation through a keyword subscription. During onboarding you subscribe English keywords; they are converted into Chinese search terms, and the system backfills the last 30 days of matching posts and translates them into English. You then read the data with three query endpoints that need no task: POST /weibo/translate/search for translated posts by date range and sort order, POST /weibo/translate/pushs for a post's translated comments by post_id, and POST /weibo/translate/reposts for an original post's translated reposts. Only posts covered by subscribed keywords are translated; arbitrary posts are not translated on demand. Data is collected by web crawlers from content publicly published on Weibo.

What teams use it for

Give analysts outside China a readable feed of Weibo discussion about their brand, industry or market.
Follow a topic in English across posts, comments and reposts.
Read the translated comments and reposts of the posts that matter without running your own translation step.

Endpoints

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

Method	Path	What it does
POST	`/weibo/translate/search`	Queries translated posts for subscribed keywords by date range, sort order and page.
POST	`/weibo/translate/pushs`	Returns the translated comments of one post by post_id.
POST	`/weibo/translate/reposts`	Returns the translated reposts of one original post by post_id.

Request parameters

POST /weibo/translate/search

Parameter	In	Type	Required	Default / allowed	Description
`endDate`	body	string	Yes		End of the date range (YYYY-MM-DD HH:MM:SS).
`page`	body	number	Yes		Page number, starting at 1.
`sorted`	body	string	Yes	`allowed tm \| _score \| like_count \| dislike_count \| comment_count \| reply_count \| share_count`	Sort field.
`startDate`	body	string	Yes		Start of the date range (YYYY-MM-DD HH:MM:SS).
`dateType`	body	string	No	`allowed post_time \| crawl_time`	Whether the date range applies to post time or crawl time.
`keywords`	body	string	No		Optional query over your subscribed coverage, in query-string syntax (for example coffee OR latte).
`pageSize`	body	number	No		Posts per page.
`request_id`	body	string	No		Optional request identifier.

POST /weibo/translate/pushs

Parameter	In	Type	Required	Default / allowed	Description
`post_id`	body	string	Yes		ID of the translated post whose comments you want.
`page`	body	number	No	`1`	Page number, starting at 1.
`pageSize`	body	number	No	`1000 (max 1000)`	Comments per page, max 1000.

POST /weibo/translate/reposts

Parameter	In	Type	Required	Default / allowed	Description
`post_id`	body	string	Yes		ID of the original post whose reposts you want.
`page`	body	number	No	`1`	Page number, starting at 1.
`pageSize`	body	number	No	`100 (max 100)`	Reposts per page, max 100.
`request_id`	body	string	No		Optional request identifier.

Response fields

Data	Fields	Endpoint
Translated posts	data, total_count	`POST /weibo/translate/search`
Translated comments	id, post_id, author, author_id, content, push_type, sentiment, tm, tm_crawler, region	`POST /weibo/translate/pushs`
Translated reposts	id, parent_id, url, author, author_id, title, content, sentiment, tm, tm_crawler, region	`POST /weibo/translate/reposts`

Code examples

curl: query translated posts

curl -X POST https://api.infominer.io/api/v2/weibo/translate/search \
  -H "auth-header: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords": "coffee OR latte", "startDate": "2026-06-01 00:00:00", "endDate": "2026-06-30 23:59:59", "dateType": "post_time", "sorted": "tm", "page": 1, "pageSize": 50}'

curl: translated comments of one post

curl -X POST https://api.infominer.io/api/v2/weibo/translate/pushs \
  -H "auth-header: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"post_id": "0000000000000001", "page": 1, "pageSize": 50}'

Python (requests)

import requests

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

# Translated posts for your subscribed keywords (no task needed)
posts = requests.post(
    f"{BASE_URL}/weibo/translate/search",
    headers=HEADERS,
    json={
        "keywords": "coffee OR latte",
        "startDate": "2026-06-01 00:00:00",
        "endDate": "2026-06-30 23:59:59",
        "dateType": "post_time",
        "sorted": "tm",
        "page": 1,
        "pageSize": 50,
    },
    timeout=30,
).json()
print(posts["total_count"], "translated posts")

# Translated comments of one post
comments = requests.post(
    f"{BASE_URL}/weibo/translate/pushs",
    headers=HEADERS,
    json={
        "post_id": "0000000000000001",
        "page": 1,
        "pageSize": 50,
    },
    timeout=30,
).json()
for row in comments.get("data", []):
    print(row["author"], row["content"][:60])

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.

POST /weibo/translate/pushs response (illustrative data)

{
  "total_count": 1,
  "data": [
    {
      "id": "0000000000000101",
      "post_id": "0000000000000001",
      "author": "sample_user_2",
      "author_id": "0000000000000002",
      "content": "The light-roast beans at this shop really are good. I want to try them this weekend.",
      "sentiment": "Positive",
      "region": "",
      "tm": 1781064000,
      "tm_crawler": 1781150400
    }
  ]
}

Limits and notes

Translation is a keyword subscription set up at onboarding; the system backfills the last 30 days of matching posts.
English keywords are converted into Chinese search terms before collection, and the translation is machine translation.
POST /weibo/translate/search requires startDate, endDate, page and sorted.
Translated comments are read up to 1000 per page and translated reposts up to 100 per page.
POST /weibo/translate/pushs returns 404 when the translated post is missing or outside the sources available to your account.

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 translate any Weibo post on demand?: No. Only posts covered by your subscribed keywords are translated. The query endpoints read translated records that already exist.
How far back does translated data go?: When you subscribe a keyword, the system backfills the last 30 days of matching posts with English machine translation.
Is the translation done by people?: No. It is machine translation. Translated comments carry post_id and translated reposts carry parent_id, so they link back to the posts they belong to.
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.