/hackernews/whoishiring

POST /api/hackernews/whoishiring

Price: 10 credits

Structured job postings from a monthly Hacker News 'Who is hiring?' thread

How to use it

Get structured job postings from a Hacker News 'Who is hiring?' monthly thread. Leave both thread_id and month empty for the latest month, pass month ('June 2026' or '2026-06') for a specific month, or thread_id for a known thread. Each posting carries the hiring company, role, compensation, location, a remote flag, the company link, the full text, the author, and the Hacker News url. Set is_remote to keep only remote or only non-remote postings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• thread_id integer nullable — Numeric id of a specific monthly thread (examples: 38842977; >: 0)
• month string nullable — Target month, e.g. 'June 2026' or '2026-06' (examples: "January 2024")
• count integer required — Max number of job postings to return (examples: 50; min: 1)
• is_remote boolean nullable — Return only postings explicitly flagged remote (true) or not remote (false)

Response

• @type string (default: "HackernewsJobPost")
• id integer required (>: 0)
• author string nullable
• created_at integer nullable
• hn_url string nullable
• text string nullable
• company string nullable
• role string nullable
• compensation string nullable
• location string nullable
• is_remote boolean nullable
• company_url string 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 — Thread not found 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.