Do I need a Weibo developer account?

No. There is no Weibo app, OAuth flow or app review. One InsightSocial API key works for this endpoint and every other platform, and your first 10 calls priced at 100 credits or less are free.

How do I get every result, not just the first page?

This endpoint pages. Each response carries pagination.next_cursor and pagination.has_more. Send next_cursor back unchanged as the cursor parameter and stop when has_more is false. Every page is a separate call and is charged as one.

What happens if the account is private or nothing is found?

You get an error or an empty result, and it costs 0 credits. The API reads public Weibo data only, so private accounts and deleted content come back as not found rather than as partial data.

Can I call the Weibo User Posts API from Claude, ChatGPT or Cursor?

Yes. Add the hosted MCP server at https://api.insightsocial.app/mcp to your AI app and sign in. The assistant finds this endpoint by name, shows its price and calls it with your credits.

GET /v1/weibo/user/posts

Weibo User Posts API

Q: How much does the Weibo User Posts API cost?

10 credits per successful call. A call that errors or finds nothing costs 0 credits, and an answer from the shared cache costs 2. Pro's 10,000 monthly credits cover about 1,000 calls at 10 credits each. Add dry_run=1 to see the price of a call without making it.

Returns a page of an account’s recent public posts, each with text, engagement counts and publish time.

Get a free API key Full API reference

10 credits a call · cursor pagination · failed calls free · 10 free calls to start

curl "https://api.insightsocial.app/v1/weibo/user/posts?user_id=1722594714" \
-H "x-api-key: $INSIGHTSOCIAL_API_KEY"

200 OKJSON

{
"success": true,
"platform": "weibo",
"endpoint": "/v1/weibo/user/posts",
"schema_version": "2",
"data": {
"items": [
{
"post": {
"id": "<string>",
"url": "<string | null>",
"kind": "<string | null>",
"content": {
"text": "<string | null>",
"media_urls": "<array | null>",
"thumbnail_url": "<string | null>",
"duration_seconds": "<number | null>"
},
"author": {
"id": "<string | null>",
"username": "<string | null>",
"display_name": "<string | null>",
"avatar_url": "<string | null>",
"verified": "<boolean | null>"
},
"engagement": {
"views": "<integer | null>",
"likes": "<integer | null>",
"comments": "<integer | null>",
"shares": "<integer | null>",
"saves": "<integer | null>"
},
"flags": {
"nsfw": "<boolean | null>",
"spoiler": "<boolean | null>",
"pinned": "<boolean | null>",
"deleted": "<boolean>",
"likes_hidden": "<boolean | null>",
"comments_hidden": "<boolean | null>",
"shares_hidden": "<boolean | null>",
"views_hidden": "<boolean | null>",
"saves_hidden": "<boolean | null>"
},
"published_at": "<string | null>",
"language": "<string | null>",
"ext": "<object | null>"
}
}
]
},
"pagination": {
"next_cursor": "<string | null>",
"has_more": "<boolean>"
},
"unavailable": [],
"credits_used": "<integer>"
}

When to use it

Use it to follow one account; for a single post use post, and for a keyword use search.

Parameters

Query parameters for GET /v1/weibo/user/posts. Send your key in the x-api-key header.

Name	Required	Description
user_id	Yes	Numeric Weibo user id (weibo.com/u/<id>).
cursor	No	The pagination.next_cursor from the previous page, sent back unchanged. Omit it for the first page.

Response fields

The same unified schema every platform returns, so code written for Weibo works on the other eight. A field the platform did not provide is null and listed in unavailable.

Field	Type	Notes
id	string	An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
url	string \| null
kind	string \| null	The format of the post. Format words only, never a platform name. short = short-form vertical video (a reel, a TikTok, a YouTube Short).
content.text	string \| null
content.media_urls	array \| null
content.thumbnail_url	string \| null
content.duration_seconds	number \| null
author.id	string \| null
author.username	string \| null
author.display_name	string \| null
author.avatar_url	string \| null
author.verified	boolean \| null
engagement.views	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
engagement.likes	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
engagement.comments	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
engagement.shares	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
engagement.saves	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
flags.nsfw	boolean \| null
flags.spoiler	boolean \| null
flags.pinned	boolean \| null
flags.deleted	boolean
flags.likes_hidden	boolean \| null
flags.comments_hidden	boolean \| null
flags.shares_hidden	boolean \| null
flags.views_hidden	boolean \| null
flags.saves_hidden	boolean \| null
published_at	string \| null	ISO-8601 timestamp in UTC, ending in Z.
language	string \| null	The content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1).
ext	object \| null	Platform-specific fields, snake_case.

Every field, error and example is in the Weibo User Posts API reference.

How much does the Weibo User Posts API cost?

10 credits per successful call.

Failed calls are free
A call that errors or finds nothing costs 0 credits.
Know the price first
Add dry_run=1 and the response quotes the call without making it. Nothing is charged.
One balance
API calls and Chrome extension exports share the same credits, on the free plan too.

See plans and credit packs How credits work