/indiehackers/posts/search

POST /api/indiehackers/posts/search

Price: 10 credits

Read an Indie Hackers post feed: the newest posts, the all-time top posts, or the top posts of a given month or week. Each row carries the title, author username, like and comment counts, plus a UTC timestamp on the newest feed.

How to use it

List Indie Hackers posts from one feed at a time. Each feed serves 200 posts, so reach older material by walking sort=top_month or sort=top_week backwards through periods rather than asking for more rows. Pass the id of a row to indiehackers/posts for the body and the comment thread, and the author username to indiehackers/users.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of posts to return (min: 1; max: 200)
• sort string — Which Indie Hackers feed to read (default: "newest"; one of: "newest", "top_all_time", "top_month", "top_week")
• period string nullable — Feed period. With sort=top_month a month as YYYY-MM, with sort=top_week the Monday that opens the week as YYYY-MM-DD. Left empty it is the current month or the current week in UTC. Rejected with sort=newest and sort=top_all_time (examples: "2026-08", "2026-09-14")

Response

• @type string (default: "IndiehackersPostCard")
• id string required
• post_title string required
• username string nullable
• user_name string nullable
• user_image string nullable
• upvote_count integer nullable
• reply_count integer nullable
• created_at integer nullable
• post_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 — Indie Hackers has no feed for this period. 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.