POST /api/fourchan/threads/archive
Price: 5 credits
List the thread numbers held in one 4chan board's archive, most recently archived first, each with the URL of the archived thread
The archive is the only route to 4chan threads that are no longer on a board, and it carries nothing but the numbers — pass each `id` with the same `board` to fourchan/threads to read the thread itself. Boards that keep no archive answer 412, and `has_archive` on fourchan/boards/search narrows the candidates beforehand, but it is the board's own declaration: `/r/` declares an archive and is still refused here, so treat a 412 on a board that declares one as that board rather than as a failed call. An archive is a rolling window of the last few days, not storage — a thread number listed today is gone for good once it rotates out. Archive depth is set per board and ranges from a single thread to over ten thousand, so a small archive is normal.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)board string required — Board slug whose archive to list, or a 4chan URL containing it (examples: "g", "v", "https://boards.4chan.org/g/"; minLength: 1)count integer required — Max number of archived threads to return (min: 1)@type string (default: "FourchanArchivedThread")id string requiredboard string requiredurl string nullable422 — board is not a board slug 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 — No such board, or this board serves no archive — including `/r/`, which declares one 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.