/fivech/threads

POST /api/fivech/threads

Price: 20 credits

Get a full 5ch (5ちゃんねる) thread by board and thread id: title, creation time, post count and every post with author name, mail, anonymous daily ID, body text, quoted post numbers and links. Live, recently archived and 2001-era historical threads are all served.

How to use it

Fetch one 5ch (5ちゃんねる) thread by 'board' (directory name such as 'newsplus') plus 'thread' (numeric thread id, which is also the unix creation timestamp, or a full read.cgi thread URL). Returns a single item with thread_title, created_at, last_post_at, post_count and posts[] (number, name, mail, text, created_at, anon_id — the per-board daily anonymous author id, be_id, reply_to post numbers, links). Threads from 2001 onwards are available; a thread id is unique inside its board only, so 'board' is always required.

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 the thread belongs to (examples: "newsplus", "poverty"; minLength: 1)
• thread string required — Thread id (the unix timestamp of thread creation) or a full thread URL (examples: "1785107074", "https://asahi.5ch.io/test/read.cgi/newsplus/1785107074/"; minLength: 1)

Response

• @type string (default: "FivechThread")
• id string required
• board string required
• url string required
• thread_title string required
• created_at integer nullable
• post_count integer (default: 0)
• last_post_at integer nullable
• posts array (default: [])
  • @type string (default: "FivechPost")
  • number integer required
  • name string nullable
  • mail string nullable
  • text string nullable
  • created_at integer nullable
  • anon_id string nullable
  • be_id string nullable
  • reply_to array (default: [])
  • links array (default: [])

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 or thread not found (well-formed input, but the board does not exist or that thread was never created on it) 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.