01 / THE USE CASE
Watch public launches without a Product Hunt client
Discovery, competitive watch, and outreach teams often need today's leaderboard plus hunter, makers, and comment threads. The Product Hunt API reads those public pages and returns a stable JSON contract.
It does not crawl the launched product's own marketing site. For that company's published emails, use the Website Contacts API on their domain.
02 / HOW TO CALL IT
List, then open a slug
GET /v1/launches lists today or a date=YYYY-MM-DD leaderboard. Optional q keeps launches whose name, tagline, slug, or topic match. Parameters live on the Product Hunt API page.
GET /v1/launches/product?slug=linear returns hunter, makers, description, images, comments, and contact. Each of those calls costs 8 credits.
03 / BOUNDARIES
Public pages, not a launch archive you resell
Do not republish the daily leaderboard as a competing launches feed. Keep Product Hunt URLs when you display a launch. For organic web results about the same product, use the SERP retrieval use case.
04 / FAQ
Questions from discovery teams
Is this Product Hunt's official API?
No. Clair reads public HTML. It does not log in, vote, comment, or call Product Hunt's private GraphQL API.
What timezone is 'today'?
Product Hunt's Pacific-time calendar day. Pass date=YYYY-MM-DD for a past leaderboard.
How do I get makers and comments?
The list endpoint is the rank index. Pass results[].slug to GET /v1/launches/product. That second call is billed separately.