/indiehackers/jobs/search

POST /api/indiehackers/jobs/search

Price: 5 credits

Search the Indie Hackers jobs board (remote founder/startup roles). Combine a free-text query with an optional product filter, ordered newest first. Each result carries role, salary range, location and the hiring product.

How to use it

Search Indie Hackers job ads. Filter by product (product slug). Each result has id, post_id, job_title, role, text (description), tags (skills / job type), min_salary, max_salary, payment_period (e.g. 'hour', 'year'), location, location_timezone, view_count, reply_count, product_id, product_name, product_tagline, user_id, username, created_at, updated_at and closed_at.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Free-text search over job title, role and description (default: ""; examples: "engineer", "designer")
• count integer required — Max number of jobs to return (min: 1)
• product string nullable — Restrict to jobs posted for a product slug (examples: "pitchmap")

Response

• @type string (default: "IndiehackersJob")
• id string required
• post_id string nullable
• job_title string nullable
• role string nullable
• text string nullable
• tags array (default: [])
• min_salary number nullable
• max_salary number nullable
• payment_period string nullable
• location string nullable
• location_timezone string nullable
• view_count integer nullable
• reply_count integer nullable
• link_click_count integer nullable
• part_number integer nullable
• product_id string nullable
• product_name string nullable
• product_tagline string nullable
• product_description string nullable
• user_id string nullable
• username string nullable
• created_at integer nullable
• updated_at integer nullable
• closed_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.