/producthunt/launches/search

POST /api/producthunt/launches/search

Price: 1 credit

Search Product Hunt (producthunt.com) launches by keyword, optional topic and featured filters

How to use it

Search Product Hunt (producthunt.com) launches by keyword. A launch is one product release on PH (a product can have many launches over time). Returns id, name, alias, url, created_at, and the parent product (id, name, tagline, alias, url, rating, review_count, image, is_offline). Optionally filter by topic name (e.g. 'Productivity', 'Artificial Intelligence') and featured-only flag.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "ai", "notion", "crm"; minLength: 1)
• topic string nullable — Filter to launches tagged with this Product Hunt topic. Must be the topic DISPLAY NAME in title case (e.g. 'Productivity', 'Artificial Intelligence', 'Notion'), not the URL slug — the upstream search index here keys on display name, while other Product Hunt endpoints (topics, categories, leaderboard) take topic as slug. (examples: "Productivity", "Artificial Intelligence")
• featured boolean — When true, only featured launches are returned (matches the site's default). (default: true)
• count integer required — Max number of launches to return (min: 1)

Response

• @type string (default: "ProductHuntSearchLaunch")
• id string required
• name string required
• alias string required
• url string required
• created_at string nullable
• product object nullable
  • @type string (default: "ProductHuntSearchLaunchProduct")
  • id string required
  • name string required
  • tagline string nullable
  • alias string required
  • url string required
  • rating number nullable
  • review_count integer nullable
  • image string nullable
  • is_offline boolean 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 — The entity was not found, or a precondition failed 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.