/fivech/boards/archive

POST /api/fivech/boards/archive

Price: 10 credits

List archived (past-log) threads of a 5ch (5ちゃんねる) board back to 2001: thread id, title, creation time and final post count. Walk from the newest or the oldest thread and restrict to a time window.

How to use it

Walk the past-log archive of one 5ch (5ちゃんねる) board — dead threads going back to 2001, which is the bulk of the site's history (a large board holds millions of archived threads). Requires 'board' (directory name) and 'count'. 'order' picks newest-first or oldest-first; 'before'/'after' are unix timestamps bounding thread creation time (a thread id IS its creation timestamp, so they can be compared directly). Each result has id, board, url, thread_title, created_at and post_count; pass id + board to the threads endpoint to read the posts.

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)
• order string — Walk the archive from the newest or from the oldest thread (default: "newest"; one of: "newest", "oldest")
• before integer nullable — Only threads created before this unix timestamp (examples: 1500000000; min: 0)
• after integer nullable — Only threads created after this unix timestamp (examples: 1000000000; min: 0)

Response

• @type string (default: "FivechThreadSummary")
• id string required
• board string required
• url string required
• thread_title string required
• created_at integer nullable
• post_count integer 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 — Board not found (well-formed directory name but no such board on 5ch) 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.