Weibo Comments API

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Weibo Comments endpoint (weibo/comments).

Endpoint contract:
- 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

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": "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

{
  "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.

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

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