/producthunt/products

POST /api/producthunt/products

Price: 5 credits

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

How to use it

Get full details of a Product Hunt (producthunt.com) product by slug or product URL. Returns name, tagline, description, rating, review_count, follower_count, image, screenshots, categories, social links, flags (is_top_product, has_alternatives, was_in_ycombinator), price, dates, pros/cons AI tags, and makers (authors).

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

Response

• @type string (default: "ProductHuntProduct")
• id string nullable
• alias string required
• name string required
• tagline string nullable
• description string nullable
• url string required
• website_url string nullable
• rating number nullable
• review_count integer nullable
• follower_count integer nullable
• post_count integer nullable
• founder_review_count integer nullable
• image string nullable
• screenshots array (default: [])
• category string nullable
• categories array (default: [])
  • @type string (default: "service__parsers__producthunt__products__products__ProductHuntCategory")
  • id string nullable
  • name string required
  • alias string nullable
• operating_system string nullable
• price number nullable
• currency string nullable
• is_top_product boolean nullable
• has_alternatives boolean nullable
• was_in_ycombinator boolean nullable
• is_offline boolean nullable
• created_at string nullable
• updated_at string nullable
• first_launched_at string nullable
• twitter_url string nullable
• linkedin_url string nullable
• instagram_url string nullable
• facebook_url string nullable
• github_url string nullable
• ios_url string nullable
• pros array (default: [])
  • @type string (default: "ProductHuntProConTag")
  • id string nullable
  • name string required
  • type string nullable
  • count integer nullable
• cons array (default: [])
  • @type string (default: "ProductHuntProConTag")
  • id string nullable
  • name string required
  • type string nullable
  • count integer nullable
• authors array (default: [])
  • @type string (default: "ProductHuntProductAuthor")
  • name string required
  • image string nullable
  • url 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.