/producthunt/products/launches

POST /api/producthunt/products/launches

Price: 5 credits

Get the list of Product Hunt (producthunt.com) launches of a product by slug or product URL

How to use it

Get the history of launches of a Product Hunt (producthunt.com) product by slug or product URL. Returns name, tagline, launch date, vote_count, comment_count, daily/weekly/monthly rank, image, awards (Golden Kitty / Top Post badges).

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "ProductHuntProductLaunch")
• id string required
• alias string required
• name string required
• tagline string nullable
• url string required
• external_url string nullable
• image string nullable
• created_at string nullable
• featured_at string nullable
• updated_at string nullable
• vote_count integer nullable
• launch_day_vote_count integer nullable
• comment_count integer nullable
• daily_rank integer nullable
• weekly_rank integer nullable
• monthly_rank integer nullable
• state string nullable
• awards array (default: [])
  • @type string (default: "ProductHuntProductLaunchAward")
  • id string nullable
  • type string required
  • category string nullable
  • position integer nullable
  • year string nullable
  • period string nullable
  • date 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 — Product 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.