/tieba/threads

POST /api/tieba/threads

Price: 5 credits

Get Tieba Thread

How to use it

Get one Baidu Tieba thread by id or tieba.baidu.com/p URL: title, bar, author with level and IP region, the opening post's text, images and videos, and reply, agree, collect and share counts. Its replies are tieba/threads/posts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• thread string required — Tieba thread id, or its tieba.baidu.com/p URL (examples: "9911924096", "https://tieba.baidu.com/p/9911924096"; minLength: 1)

Response

• @type string (default: "TiebaThread")
• id string required
• url string required
• forum object nullable
  • @type string (default: "TiebaForumRef")
  • id string required
  • name string required
  • url string required
  • category string nullable
  • subcategory string nullable
  • image string nullable
• author object nullable
  • @type string (default: "TiebaUser")
  • id string required
  • name string nullable
  • display_name string nullable
  • image string nullable
  • level integer nullable
  • level_name string nullable
  • gender string nullable
  • ip_location string nullable
  • manager_title string nullable
• created_at integer nullable
• text string nullable
• images array (default: [])
• videos array (default: [])
  • @type string (default: "TiebaVideo")
  • url string required
  • thumbnail string nullable
  • duration_seconds integer nullable
  • view_count integer nullable
  • width integer nullable
  • height integer nullable
  • size_bytes integer nullable
• reply_count integer nullable
• agree_count integer nullable
• disagree_count integer nullable
• collect_count integer nullable
• share_count integer nullable
• is_excellent boolean nullable
• first_post_id 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 — Thread not found or deleted. Check the id or URL. 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.