raw.tieba.threadTieba thread
https://api.qovia.ai/v1/raw/tieba/threadOpening post of a thread (text, author, likes/saves/shares/replies, forum) plus one page of floors, about 15 per page in floor order, each with its author's nickname, level and IP location. Use raw.tieba.replies for replies inside a floor. Deleted or unknown threads answer 404 and a page past the end answers empty; neither is charged.
Typical uses: Tracking a single post or product: reach, engagement over time and archiving.
- Price
- $0.0015 / call$1.5 per 1k$1 per 1k after 5M a month
- Billing
- Charged only for successful, non-empty resultsthe charge is in meta.charged_usd
- Scope
raw:tiebaThe API key needs this scope- Rate limit
- NoneNo per-account or per-endpoint request limit
Parameters
Only these parameters are accepted; any other one returns 400.
thread_idThread ID (the number after tieba.baidu.com/p/)
Pattern^[1-9][0-9]{0,19}$Example
10693684727pageReply page, from 1; only page 1 carries the opening post's full text and images
Default1Range1–10000
Response
A success is HTTP 200 with the shared envelope: request_id, data (this endpoint's data, see the example) and meta (the charge). An empty result is also 200, with meta.empty true, not charged, and data may be an empty structure or null.
Errors
| code | HTTP | Billing | Description |
|---|---|---|---|
scope_denied | 403 | Not charged | This API key lacks the scope the endpoint requires. |
endpoint_unavailable | 503 | Not charged | The endpoint is not available right now (no data source connected yet, or no price configured); nothing ran. |
invalid_params | 400 | Not charged | The parameters failed validation: a required one is missing, a type or format is wrong, an array has more items than allowed, an unknown one was sent, or the POST body is not a JSON object. An error in one parameter starts with its name (item_id: …); a missing or unknown parameter starts with params: …. |
insufficient_balance | 402 | Not charged | The balance cannot pay for this call; top up first. |
upstream_busyRetryable | 503 | Refunded | The data source is busy or cooling down; refunded. Retry after Retry-After. |
upstream_timeout | 504 | Refunded | The data source timed out; refunded. |
upstream_error | 502 / 503 | Refunded | The data source failed; refunded. |
upstream_rejected | 400 | Refunded | The data source rejected these parameters (well-formed, but not accepted); refunded. |
not_found | 404 | Refunded | The data source has no such item (deleted, or the ID does not exist); refunded. |
reservation_expired | 504 | Refunded | The call took too long and was refunded automatically; no data is returned. |
Any request can also fail authentication: 401 invalid_api_key, 403 account_disabled, 429 too_many_auth_failures.
Needs an account with a balance; playground calls are billed like API calls.