GET /v1/weibo/post/comments
Weibo Post Comments API
Returns a page of first-level comments on a post, each with text, author, likes, reply count and time.
10 credits a call · cursor pagination · failed calls free · 10 free calls to start
curl "https://api.insightsocial.app/v1/weibo/post/comments?post_id=5283919831764022" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
When to use it
Use it when you have a post id and want the conversation under it.
Parameters
Query parameters for GET /v1/weibo/post/comments. Send your key in the x-api-key header.
| Name | Required | Description |
|---|---|---|
| post_id | Yes | Weibo post id (the number in the post URL). |
| limit | No | Comments per page, 1 to 20. Default 10. |
| 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 | |
| parent_id | string | null | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| post_id | string | null | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| text | string | null | |
| author.id | string | null | |
| author.username | string | null | |
| author.display_name | string | null | |
| author.avatar_url | string | null | |
| author.verified | boolean | null | |
| engagement.likes | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.replies | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| flags.pinned | boolean | null | |
| flags.deleted | boolean | |
| 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). |
| replies | array | null | |
| ext | object | null | Platform-specific fields, snake_case. |
Every field, error and example is in the Weibo Post Comments API reference.
How much does the Weibo Post Comments 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.
Weibo Post Comments API: frequently asked questions
Send GET /v1/weibo/post/comments with the post_id parameter and your key in the x-api-key header. Returns a page of first-level comments on a post, each with text, author, likes, reply count and time.
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.
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.
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.
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.
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.