/fivech/boards/threads

POST /api/fivech/boards/threads

Price: 1 credit

List the live threads of a 5ch (5ちゃんねる) board: thread id, title, creation time, post count and momentum (posts per day). Order by bump, creation time, post count or momentum, and filter by title.

How to use it

List the threads currently alive on one 5ch (5ちゃんねる) board (identified by its directory name, e.g. 'newsplus'). Default order 'bump' is the board's own ordering — most recently posted-to first; 'created', 'post_count' and 'momentum' reorder the same set. 'keyword' filters by thread title. Each result has id (also the unix creation timestamp), board, url, thread_title, created_at, post_count and momentum (posts per day). Threads die at ~1000 posts and then move to the archive.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• board string required — Board directory name (examples: "newsplus", "poverty"; minLength: 1)
• count integer required — Max number of results to return (min: 1)
• sort string — Ordering applied to the board's threads (default: "bump"; one of: "bump", "created", "post_count", "momentum")
• keyword string — Filter threads whose title contains this text (default: ""; examples: "速報")

Response

• @type string (default: "FivechBoardThread")
• id string required
• board string required
• url string required
• thread_title string required
• created_at integer nullable
• post_count integer nullable
• momentum number 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 — The entity was not found, or a precondition failed 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.