/producthunt/launches/comments

POST /api/producthunt/launches/comments

Price: 2 credits

Get Product Hunt (producthunt.com) launch comments thread by launch slug or URL

How to use it

Get the discussion comments thread of a Product Hunt (producthunt.com) launch, by launch slug or URL. Launch comments are the conversation under one launch (separate from product reviews) — makers, hunters and community members reply to the launch announcement. Each top-level comment carries text, author, upvote_count, badges (e.g. 'maker', 'hunter'), created_at, and nested replies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• launch string required — Product Hunt launch slug ('notion-calendar') or full launch URL ('https://www.producthunt.com/products/notion?launch=notion-calendar'). (examples: "notion-calendar", "https://www.producthunt.com/products/notion?launch=notion-calendar"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?producthunt\.com[^\s]*|[A-Za-z0-9][A-Za-z0-9._-]*)$)
• count integer required — Max number of top-level comment threads to return (min: 1)

Response

• @type string (default: "ProductHuntLaunchComment")
• id string required
• text string nullable
• body_html string nullable
• url string nullable
• created_at string nullable
• upvote_count integer nullable
• reply_count integer nullable
• is_sticky boolean nullable
• is_pinned boolean nullable
• badges array (default: [])
• parent_id string nullable
• author object nullable
  • @type string (default: "ProductHuntLaunchCommentAuthor")
  • id string required
  • name string required
  • alias string nullable
  • image string nullable
  • is_verified boolean nullable
  • is_ambassador boolean nullable
  • is_prominent boolean nullable
  • byline_product object nullable
    • @type string (default: "ProductHuntLaunchCommentBylineProduct")
    • id string required
    • alias string required
    • name string required
• 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 — Launch 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.