/producthunt/launches

POST /api/producthunt/launches

Price: 1 credit

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

How to use it

Get full details of a single Product Hunt (producthunt.com) launch by slug or URL. A launch is one product release on PH (a product can have many launches over time). Returns name, tagline, description, launch_date, daily/weekly rank, upvote_count, comment_count, image, media (screenshots + videos), topics, badges (GoldenKitty/TopPost awards), hunter (who posted), makers (the team), product reference, and website_url.

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._-]*)$)

Response

• @type string (default: "ProductHuntLaunch")
• id string required
• alias string required
• name string required
• tagline string nullable
• description string nullable
• url string required
• launch_number integer nullable
• launch_date string nullable
• created_at string nullable
• scheduled_at string nullable
• updated_at string nullable
• daily_rank integer nullable
• weekly_rank integer nullable
• upvote_count integer nullable
• launch_day_score integer nullable
• comment_count integer nullable
• launch_state string nullable
• product_state string nullable
• pricing_type string nullable
• is_top_launch boolean nullable
• is_available boolean nullable
• is_featured boolean nullable
• is_launching_today boolean nullable
• is_launched_this_week boolean nullable
• image string nullable
• website_url string nullable
• product object nullable
  • @type string (default: "ProductHuntLaunchProduct")
  • id string required
  • alias string required
  • name string required
  • tagline string nullable
  • image string nullable
  • rating number nullable
  • is_top_product boolean nullable
  • is_offline boolean nullable
• hunter object nullable
  • @type string (default: "ProductHuntLaunchUser")
  • id string required
  • name string required
  • alias string nullable
  • headline string nullable
  • image string nullable
• makers array (default: [])
  • @type string (default: "ProductHuntLaunchUser")
  • id string required
  • name string required
  • alias string nullable
  • headline string nullable
  • image string nullable
• topics array (default: [])
  • @type string (default: "ProductHuntLaunchTopic")
  • id string required
  • name string required
  • alias string nullable
  • url string nullable
• media array (default: [])
  • @type string (default: "ProductHuntLaunchMedia")
  • type string required
  • image string nullable
  • width integer nullable
  • height integer nullable
  • video_url string nullable
  • video_platform string nullable
  • video_id string nullable
• badges array (default: [])
  • @type string (default: "ProductHuntLaunchBadge")
  • id string required
  • type string required
  • position integer nullable
  • period string nullable
  • date string nullable
  • year string nullable
  • category string nullable
• links array (default: [])
  • @type string (default: "ProductHuntLaunchLink")
  • name string required
  • website string nullable
  • redirect_path string nullable
  • devices 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.