/producthunt/forums/threads

POST /api/producthunt/forums/threads

Price: 10 credits

Get Product Hunt (producthunt.com) forum thread (title, body, author, forum, nested comments) by URL or forum/thread slug pair

How to use it

Get a Product Hunt (producthunt.com) forum thread (discussion under /p/<forum>/<thread>) by URL or compact '<forum-slug>/<thread-slug>' pair. Returns title, text, author profile, forum context (slug + category), upvote/comment/page-view counters, and a nested comments tree (each comment carries author, text, created_at, vote_count, and inline replies).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• thread string required — Product Hunt forum thread — full URL ('https://www.producthunt.com/p/general/<thread-slug>') or compact '<forum-slug>/<thread-slug>' pair. (examples: "https://www.producthunt.com/p/general/how-do-you-decide-what-features-should-be-free-and-what-should-be-paid", "general/how-do-you-decide-what-features-should-be-free-and-what-should-be-paid"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?producthunt\.com[^\s]*|[A-Za-z0-9][A-Za-z0-9._-]*/[A-Za-z0-9][A-Za-z0-9._-]*)$)
• count integer required — Max number of top-level comments to return (min: 1)

Response

• @type string (default: "ProductHuntForumThread")
• id string required
• alias string required
• text string nullable
• body_html string nullable
• url string required
• author object nullable
  • @type string (default: "ProductHuntForumUser")
  • id string nullable
  • name string nullable
  • alias string nullable
  • image string nullable
  • is_verified boolean nullable
  • is_ambassador boolean nullable
  • is_prominent boolean nullable
• forum object nullable
  • @type string (default: "ProductHuntForum")
  • id string nullable
  • alias string required
  • name string nullable
  • description string nullable
  • category_id string nullable
  • category_alias string nullable
  • category_name string nullable
• created_at string nullable
• vote_count integer nullable
• comment_count integer nullable
• page_view_count integer nullable
• is_featured boolean nullable
• is_pinned boolean nullable
• status string nullable
• comments array (default: [])
  • @type string (default: "ProductHuntForumComment")
  • id string required
  • parent_id string nullable
  • text string nullable
  • body_html string nullable
  • author object nullable
    • @type string (default: "ProductHuntForumUser")
    • id string nullable
    • name string nullable
    • alias string nullable
    • image string nullable
    • is_verified boolean nullable
    • is_ambassador boolean nullable
    • is_prominent boolean nullable
  • created_at string nullable
  • vote_count integer nullable
  • reply_count integer nullable
  • url string nullable
  • is_pinned boolean nullable
  • is_sticky boolean nullable
  • is_hidden boolean nullable
  • replies array (default: [])

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 — Forum 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.