GET /v1/weibo/profile
Weibo Profile API
Returns a public Weibo account: name, bio, avatar, follower, following and post counts, verification, location and website.
10 credits a call · single call · failed calls free · 10 free calls to start
curl "https://api.insightsocial.app/v1/weibo/profile?user_id=1722594714" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
When to use it
Use it when you have a numeric user id; for the account’s posts use user/posts.
Parameters
Query parameters for GET /v1/weibo/profile. Send your key in the x-api-key header.
| Name | Required | Description |
|---|---|---|
| user_id | Yes | Numeric Weibo user id (weibo.com/u/<id>). |
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. |
| username | string | null | |
| display_name | string | null | |
| avatar_url | string | null | |
| bio | string | null | |
| verified | boolean | null | |
| followers | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| followers_approximate | boolean | null | |
| following | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| posts_count | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| likes_count | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| url | string | null | |
| location | string | null | |
| external_url | string | null | |
| private | boolean | null | |
| joined_at | string | null | ISO-8601 timestamp in UTC, ending in Z. |
| last_post_at | string | null | ISO-8601 timestamp in UTC, ending in Z. |
| ext | object | null | Platform-specific fields, snake_case. |
Every field, error and example is in the Weibo Profile API reference.
How much does the Weibo Profile 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 Profile API: frequently asked questions
Send GET /v1/weibo/profile with the user_id parameter and your key in the x-api-key header. Returns a public Weibo account: name, bio, avatar, follower, following and post counts, verification, location and website.
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.
One call returns the profile in the data object of the standard response envelope. Fields the platform did not provide are listed in unavailable, so a null there means unknown, not zero.
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.