/weibo/users/statuses

POST /api/weibo/users/statuses

Price: 5 credits

Get Weibo User Posts

How to use it

Get posts published by a Weibo user, identified by numeric user id or profile URL. Returns each post's text, timestamp, source, media images, attached video or topic, engagement counts, and author.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Weibo user. Accepts a numeric user id or a profile URL. (examples: "2803301701"; minLength: 1)
• count integer required — Max result count (examples: 20; min: 1)

Response

• @type string (default: "WeiboStatus")
• id string required
• bid string nullable
• text string nullable
• created_at string nullable
• source string nullable
• region string nullable
• repost_count integer nullable
• comment_count integer nullable
• like_count integer nullable
• is_long_text boolean (default: false)
• pic_num integer nullable
• images array (default: [])
• user object nullable
  • @type string (default: "WeiboUser")
  • id string required
  • screen_name string required
  • description string nullable
  • image string nullable
  • cover string nullable
  • gender string nullable
  • follower_count integer nullable
  • following_count integer nullable
  • status_count integer nullable
  • is_verified boolean (default: false)
  • verified_type integer nullable
  • verified_reason string nullable
  • is_svip boolean (default: false)
  • mbrank integer nullable
  • mbtype integer nullable
  • urank integer nullable
  • profile_url string nullable
• page_info object nullable
  • @type string (default: "WeiboPageInfo")
  • type string nullable
  • object_type integer nullable
  • object_id string nullable
  • url string nullable
  • image string nullable
  • video_url string nullable
  • duration number nullable
• retweeted_status object nullable (see schema WeiboStatus)
• url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — User not found. Verify the user id. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.