POST /api/fourchan/threads/search
Price: 20 credits
List the threads currently live on one 4chan board, stickied threads first and the rest newest bump first, each with its subject, opening-post text, attached file, reply and image counts and a preview of its trailing replies. Narrow by keyword or by minimum reply count
The board's stickied threads head the list whatever their bump time, so the first rows can be years older than the rest — `is_sticky` marks them, and a small `count` may return nothing else. This is the whole live board, not a site-wide search: pick the board first with fourchan/boards/search, because 4chan has no cross-board search of any kind. `query` and `min_reply_count` are applied to that board's threads after they are read, so a term that matches nothing returns an empty list rather than an error. `replies` here is a short trailing preview and `omitted_post_count` says how many were left out — pass the `id` to fourchan/threads for every post. Threads drop off the board within hours, so a thread listed now may already be gone when you fetch it.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)board string required — Board slug to list, or a 4chan URL containing it (examples: "g", "vrpg", "https://boards.4chan.org/g/"; minLength: 1)count integer required — Max number of threads to return (min: 1)query string nullable — Keep only threads whose subject, opening-post text or URL slug contains this text, matched case-insensitively (examples: "linux", "thinkpad"; minLength: 1)min_reply_count integer nullable — Keep only threads with at least this many replies (examples: 50; min: 0)@type string (default: "FourchanThread")id string requiredboard string requiredurl string nullablealias string nullabletext string nullabletext_html string nullablecreated_at integer nullablelast_modified_at integer nullablearchived_at integer nullablereply_count integer nullableimage_count integer nullableomitted_post_count integer nullableomitted_image_count integer nullableis_sticky boolean nullableis_closed boolean nullableis_archived boolean nullableis_bump_limit_reached boolean nullableis_image_limit_reached boolean nullableauthor_name string nullabletripcode string nullablecapcode string nullableposter_id string nullablecountry string nullablecountry_name string nullableboard_flag string nullableboard_flag_name string nullablepass_since_year integer nullabletag string nullablefile object nullable@type string (default: "FourchanFile")name string nullableextension string nullableurl string nullablethumbnail string nullablewidth integer nullableheight integer nullablethumbnail_width integer nullablethumbnail_height integer nullablesize integer nullablemd5 string nullableis_spoiler boolean nullableis_deleted boolean nullablehas_mobile_variant boolean nullablespoiler_id integer nullablereplies array (default: [])@type string (default: "FourchanPost")id string requiredboard string requiredthread_id string requiredurl string nullablecreated_at integer nullabletext string nullabletext_html string nullableauthor_name string nullabletripcode string nullablecapcode string nullableposter_id string nullablecountry string nullablecountry_name string nullableboard_flag string nullableboard_flag_name string nullablepass_since_year integer nullablefile object nullable@type string (default: "FourchanFile")name string nullableextension string nullableurl string nullablethumbnail string nullablewidth integer nullableheight integer nullablethumbnail_width integer nullablethumbnail_height integer nullablesize integer nullablemd5 string nullableis_spoiler boolean nullableis_deleted boolean nullablehas_mobile_variant boolean nullablespoiler_id integer 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 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.