Weibo Posts by user API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Page through the posts a Weibo account published itself, newest first, by numeric UID. Up to 20 per page and the count varies; recommended posts from other accounts are left out. Filter to original, video or image posts with post_type. Long posts show only their opening lines here, so use post_detail for the full text and view count.
Price $0.81 per 1,000 requests ($0.000806 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Please help me write a data collection script with the EveryInfra Weibo Posts by user endpoint (weibo/user_posts).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to weibo and action to user_posts, and put the parameters inside params.
- Required parameters:
- user_id: The account's numeric Weibo UID, or a profile link containing /u/<UID>. Nicknames are not accepted; find the UID with user_search first.
- Optional parameters:
- page_token: Page token for user_posts. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received, with the other parameters unchanged.
- post_type: Which posts user_posts returns: all (default), original for the account's original posts, video or image. (allowed: all / image / original / video)
- Returns a list of records. Main fields of each record: id, url, text, posted_at, device (Client the post was published from (suc…), repost_count, comment_count, like_count, view_count (Read count Weibo shows for the post (po…), is_repost (Whether the post is a repost), original_post_id (For a repost, the ID of the original po…), is_long_text (Whether the post is a long post (post_d…); 25 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=weibo.
- Example request body:
{
"platform": "weibo",
"action": "user_posts",
"params": {
"user_id": "1749127163"
}
}
- Price: $0.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | weibo | Platform identifier, fixed value. |
action | body | string | Yes | user_posts | Capability identifier, fixed value. |
user_id | body.params | string | Yes | - | The account's numeric Weibo UID, or a profile link containing /u/<UID>. Nicknames are not accepted; find the UID with user_search first. |
page_token | body.params | string | No | - | Page token for user_posts. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received, with the other parameters unchanged. Pages hold up to 20 of the account's own posts, newest first, and vary in size; each page is one call. Tokens last 24 hours, and the last page has no next_page_token. |
post_type | body.params | string (enum) | No | - | Which posts user_posts returns: all (default), original for the account's original posts, video or image.Allowed valuesallimageoriginalvideo |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "weibo",
"action": "user_posts",
"params": {
"user_id": "1749127163"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
{
"id": "req_…",
"platform": "weibo",
"action": "user_posts",
"results": [
{
"id": …,
"url": …,
"text": …,
"posted_at": …,
"device": …,
"repost_count": …,
"comment_count": …,
"like_count": …,
"view_count": …,
"is_repost": …,
"original_post_id": …,
"is_long_text": …,
"author_id": …,
"author_name": …,
"author_bio": …,
"author_follower_count": …,
"author_following_count": …,
"author_verified": …,
"author_verified_reason": …,
"author_avatar_url": …,
"image_urls": …,
"video_url": …,
"duration_sec": …,
"duration_seconds": …,
"platform": …,
"next_page_token": …
}
],
"next_page_token": …,
"pagination": { … },
"count": …,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
device | Client the post was published from (such as an iPhone client). |
repost_count | Reposts (as distinct from quote posts). null means not disclosed. |
comment_count | Comments. null means not disclosed, not 0. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
view_count | Read count Weibo shows for the post (post_detail); user_posts list rows do not carry it. |
is_repost | Whether the post is a repost. |
original_post_id | For a repost, the ID of the original post (post_detail / user_posts); pass it as url to post_detail to read the original. Absent when the post is not a repost. |
is_long_text | Whether the post is a long post (post_detail / user_posts). On user_posts, a long post's text holds only its opening (about 140 characters). |
author_id | Author's unique ID on the platform. |
author_name | Author's display name. |
author_bio | Author bio. |
author_follower_count | Author's follower count. null means not disclosed. |
author_following_count | Number of accounts the author follows. |
author_verified | Whether the author carries Weibo verification (the V badge). |
author_verified_reason | Verification description (such as a company role); use it to tell what a verified account represents. |
author_avatar_url | Author avatar URL. |
image_urls | Array of image links in the platform's display order; absent when there are no images. |
video_url | Video link of the post. |
duration_sec | Video length in seconds (video posts on post_detail / user_posts). |
duration_seconds | Duration in seconds. null for content that is not video or audio. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
next_page_token | Page token (user_search, user_posts, topic_search, user_post_search): pass it back unchanged as page_token for the next page. Every row of a page carries the same value, which also appears at the top level of the response; absent on the last page. |
Errors and billing
- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.