/fourchan/threads

POST /api/fourchan/threads

Price: 10 credits

Get one 4chan thread by board and thread number: the opening post with its subject, text, attached file and poster flair, plus every reply in posting order with its own text and file

How to use it

Thread numbers are per board, so the pair must match: a real number on the wrong board is a 412 exactly like a number that never existed. 4chan threads are deleted once they fall off the board, and a deleted thread returns the same 412 as a wrong id, so a not-found here never means the thread was fake. Threads that reached a board's archive keep answering, with `is_archived` and `archived_at` set, but only while they stay inside the board's archive window: the archive is a rolling window, not storage, so a thread that rotates out of it 412s permanently, same as one that was never archived. Boards without an archive lose their threads outright as soon as they fall off the board. Read `text` for plain reply text and `text_html` when the quote links matter.

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 slug the thread lives on, or a 4chan URL containing it (examples: "g", "vrpg", "https://boards.4chan.org/g/thread/109781529"; minLength: 1)
• thread_id string required — Thread number, or a thread URL containing it (examples: "109781529", "https://boards.4chan.org/g/thread/109781529"; minLength: 1)

Response

• @type string (default: "FourchanThread")
• id string required
• board string required
• url string nullable
• alias string nullable
• text string nullable
• text_html string nullable
• created_at integer nullable
• last_modified_at integer nullable
• archived_at integer nullable
• reply_count integer nullable
• image_count integer nullable
• omitted_post_count integer nullable
• omitted_image_count integer nullable
• is_sticky boolean nullable
• is_closed boolean nullable
• is_archived boolean nullable
• is_bump_limit_reached boolean nullable
• is_image_limit_reached boolean nullable
• author_name string nullable
• tripcode string nullable
• capcode string nullable
• poster_id string nullable
• country string nullable
• country_name string nullable
• board_flag string nullable
• board_flag_name string nullable
• pass_since_year integer nullable
• tag string nullable
• file object nullable
  • @type string (default: "FourchanFile")
  • name string nullable
  • extension string nullable
  • url string nullable
  • thumbnail string nullable
  • width integer nullable
  • height integer nullable
  • thumbnail_width integer nullable
  • thumbnail_height integer nullable
  • size integer nullable
  • md5 string nullable
  • is_spoiler boolean nullable
  • is_deleted boolean nullable
  • has_mobile_variant boolean nullable
  • spoiler_id integer nullable
• replies array (default: [])
  • @type string (default: "FourchanPost")
  • id string required
  • board string required
  • thread_id string required
  • url string nullable
  • created_at integer nullable
  • text string nullable
  • text_html string nullable
  • author_name string nullable
  • tripcode string nullable
  • capcode string nullable
  • poster_id string nullable
  • country string nullable
  • country_name string nullable
  • board_flag string nullable
  • board_flag_name string nullable
  • pass_since_year integer nullable
  • file object nullable
    • @type string (default: "FourchanFile")
    • name string nullable
    • extension string nullable
    • url string nullable
    • thumbnail string nullable
    • width integer nullable
    • height integer nullable
    • thumbnail_width integer nullable
    • thumbnail_height integer nullable
    • size integer nullable
    • md5 string nullable
    • is_spoiler boolean nullable
    • is_deleted boolean nullable
    • has_mobile_variant boolean nullable
    • spoiler_id integer nullable

Errors

• 422 — board is not a board slug, or thread_id is not a thread number 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 thread with that number on that board — wrong pairing, or the thread has been pruned 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.