/indiehackers/posts

POST /api/indiehackers/posts

Price: 20 credits

Get one Indie Hackers post by id or URL, with its body and full comment thread

How to use it

Read one Indie Hackers post in full: the body text, the author's username, the like and comment counts, and every comment with its author, score, nesting level and timestamp. Take the id from a row of indiehackers/posts/search or from the last path segment of an indiehackers.com/post/ URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — Post id as returned by posts/search, or a post URL (examples: "i-built-a-git-host-where-ai-agents-dont-need-accounts-1dca7d2ac4", "https://www.indiehackers.com/post/live-on-product-hunt-UoYavv7glbnKg22D2xjp"; minLength: 1)

Response

• @type string (default: "IndiehackersPost")
• id string required
• post_title string required
• text string nullable
• product_id string nullable
• product_name string nullable
• username string nullable
• user_id 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
• comments array (default: [])
  • @type string (default: "IndiehackersComment")
  • id string required
  • text string nullable
  • score integer nullable
  • username string nullable
  • user_id string nullable
  • user_name string nullable
  • user_image string nullable
  • level integer nullable
  • created_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 — No Indie Hackers post with this id. 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.