Weibo Comments API

POST

API health

24h health: Mostly down

Healthy / normal
Available
Limited
Mostly down

Mostly down

Last 24 hours

Last 30 days

Read comments on a Weibo post, up to 50 per call, with text, likes, commenter and time. Pass a /detail/ link or the numeric post ID. Short links that contain letters do not work, and the full reply tree is not promised.

Send POST https://api.everyinfra.com/api/v1/social with platform set to weibo and action set to comments. Price $0.56 per 1,000 requests ($0.000556 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 Comments endpoint (weibo/comments).

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 comments, and put the parameters inside params.
- Required parameters:
  - url: Specifies the post URL or numeric post ID for the comments action. Format as /detail/NUMERIC_POST_ID or pass the numeric ID directly. Short links that contain letters are not supported.
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, text, like_count, author_id, author_name, author_avatar_url (Author avatar URL), post_id, post_url, posted_at.
- Example request body:
{
  "platform": "weibo",
  "action": "comments",
  "params": {
    "url": "https://weibo.com/1659899634/5326504200510190"
  }
}
- Price: $0.56 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	`comments`	Capability identifier, fixed value.
`url`	body.params	`string`	Yes	-	Specifies the post URL or numeric post ID for the comments action. Format as /detail/NUMERIC_POST_ID or pass the numeric ID directly. Short links that contain letters are not supported.
`limit`	body.params	`integer (1–50)`	No	`20`	The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

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": "comments",
  "params": {
    "url": "https://weibo.com/1659899634/5326504200510190"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

json

{  "id": "req_…",  "platform": "weibo",  "action": "comments",  "results": [    {      "id": …,      "text": …,      "like_count": …,      "author_id": …,      "author_name": …,      "author_avatar_url": …,      "post_id": …,      "post_url": …,      "posted_at": …,      "platform": …    }  ],  "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.
`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).
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`author_id`	Author's unique ID on the platform.
`author_name`	Author's display name.
`author_avatar_url`	Author avatar URL.
`post_id`	Keeps the platform's own meaning
`post_url`	Keeps the platform's own meaning
`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.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

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.

Errors

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

Weibo: Conversion Guidelines for Base62 MIDs and Numeric IDs ↗
Legacy Weibo developer documentation separates MID from numeric ID and specifies that letter-containing MIDs use base62 encoding. This reference only cites identifier differences and does not guarantee the legacy API is callable; `comments` on this page lack automatic conversion capabilities, so links using numeric post IDs are preferred.
Checked 2026-09-04