/indiehackers/posts/search

POST /api/indiehackers/posts/search

Price: 5 credits

Search Indie Hackers community discussions and posts by free-text query. Optionally restrict to a community group, and sort by popularity or recency. Returns post title, body, group, upvote and reply counts, author, and any linked resource.

How to use it

Full-text search over 100k+ Indie Hackers founder discussions. Filter by group (community group name); sort by popular or newest. Each result has id, item_id, item_key, item_type, post_title, text (markdown body), group_name, upvote_count, reply_count, link_click_count, part_number, is_featured, has_poll, link_url/link_title/link_description/link_image (for link posts), user_id, username, created_at and updated_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 discussion title and body (default: ""; examples: "stripe", "seo")
• count integer required — Max number of posts to return (min: 1)
• sort string — Result ordering (default: "popular"; one of: "popular", "newest")
• group string nullable — Restrict to a community group by name (examples: "Growth", "Ideas and Validation", "Building in Public", "AMAs")

Response

• @type string (default: "IndiehackersPost")
• id string required
• item_id string nullable
• item_key string nullable
• item_type string nullable
• post_title string nullable
• text string nullable
• group_name string nullable
• upvote_count integer nullable
• reply_count integer nullable
• link_click_count integer nullable
• part_number integer nullable
• is_featured boolean (default: false)
• has_poll boolean (default: false)
• link_url string nullable
• link_title string nullable
• link_description string nullable
• link_image string nullable
• user_id string nullable
• username string nullable
• created_at integer nullable
• updated_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.