/fivech/threads/search

POST /api/fivech/threads/search

Price: 5 credits

Search 5ch (5ちゃんねる) threads by keyword. Matching runs against thread titles of currently active threads across every board, and the source caps the result set at 100 threads per keyword.

How to use it

Search active 5ch (5ちゃんねる) threads by keyword across all boards. Matching is fuzzy and covers thread TITLES only — post bodies and archived threads are not searchable here, and the source never returns more than 100 threads for a keyword. Use 'mode' to pick plain or AI-assisted matching (they return different sets) and 'sort' to order by momentum (posts per day), last_post, post_count, newest or oldest. Each result has id, board, board_name, url, thread_title, created_at, post_count, momentum and last_post_at.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Keyword matched against thread titles (examples: "ニュース", "円安"; minLength: 1)
• count integer required — Max number of results to return (min: 1; max: 100)
• mode string — Matching engine: plain title matching or the AI-assisted one (default: "normal"; one of: "normal", "ai")
• sort string — Ordering applied to the matched threads (default: "momentum"; one of: "momentum", "last_post", "post_count", "newest", "oldest")

Response

• @type string (default: "FivechSearchThread")
• id string required
• board string required
• url string required
• thread_title string required
• created_at integer nullable
• post_count integer nullable
• board_name string nullable
• momentum number nullable
• last_post_at 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 — 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.