Product Hunt APIproducthunt.com ↗
Fetch Product Hunt daily leaderboards, product details, search results, and date-range aggregations. Returns upvotes, makers, topics, reviews, and links.
What is the Product Hunt API?
This API exposes 4 endpoints covering Product Hunt's daily leaderboards, product detail pages, and keyword search. The get_daily_leaderboard endpoint returns every product launched on a given date, ranked by community upvotes, while get_product_details surfaces per-product data including maker profiles, topic tags, external links, and review counts. Date-range aggregation and paginated search are also available.
curl -X GET 'https://api.parse.bot/scraper/2a0c4ef0-72ba-45b0-a96f-4dc0cdb8c915/get_daily_leaderboard?day=4&year=2026&month=7' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace producthunt-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.product_hunt_api import ProductHunt, LeaderboardEntry, SearchResult, Product, ProductNotFound
ph = ProductHunt()
# Search for AI products and iterate results
for result in ph.products.search(query="AI", limit=5):
print(result.name, result.slug, result.reviews_rating, result.reviews_count)
# Get full product details from a search result
product = ph.products.get(slug="claude")
print(product.name, product.reviews_rating, product.followers_count)
for maker in product.makers:
print(maker.name, maker.url)
# Browse the daily leaderboard
for entry in ph.leaderboards.daily(year=2026, month=6, day=8):
print(entry.rank, entry.name, entry.upvotes, entry.tagline)
# Drill into full details
details = entry.details()
print(details.description, details.website_url)
# Aggregate leaderboard over a date range
for entry in ph.leaderboards.date_range(start_date="2026-06-01", end_date="2026-06-08", limit=5):
print(entry.rank, entry.name, entry.upvotes, entry.topics)
Fetch all product launches from the daily leaderboard for a given date. Returns products ranked by community votes for that day. Each item includes rank, name, slug, tagline, topics, and upvote count. Only the top ~8 featured products are returned per day.
| Param | Type | Description |
|---|---|---|
| day | integer | Day (1-31). Omitting defaults to current UTC day. |
| year | integer | Year (YYYY). Omitting defaults to current UTC year. |
| month | integer | Month (1-12). Omitting defaults to current UTC month. |
{
"type": "object",
"fields": {
"date": "string in YYYY-MM-DD format representing the queried date",
"items": "array of product objects ranked by upvotes for the given day"
},
"sample": {
"data": {
"date": "2026-06-08",
"items": [
{
"name": "Honen",
"rank": 1,
"slug": "honen",
"topics": [
"Productivity",
"Education",
"Artificial Intelligence"
],
"tagline": "Automated teaching + learning infrastructure for any company",
"upvotes": 507
}
]
},
"status": "success"
}
}About the Product Hunt API
Leaderboards and Date Ranges
The get_daily_leaderboard endpoint accepts day, month, and year integers and returns a date string alongside an items array. Each item includes rank, name, slug, tagline, topics, and upvotes for that day's launches. All three date parameters are optional and default to the current UTC date, so omitting them returns today's leaderboard. The get_leaderboard_date_range endpoint accepts start_date and end_date in YYYY-MM-DD format and aggregates across all days in that window, deduplicating by slug and returning the top products sorted by total upvotes. An optional limit parameter caps the result size.
Product Details
get_product_details takes a slug (for example, claude or ollama) and returns a full product record: name, tagline, description, website_url, twitter_url, a media array of screenshot URLs, a makers array with each maker's name, url, and avatar_url, a topics array of tag strings, and an integer reviews_count. This endpoint is the right place to enrich leaderboard slugs with structured metadata.
Search
search_products accepts a required query string and an optional page integer. Results are paginated at 10 items per page. Each item in the items array carries id, name, slug, tagline, reviews_rating, and reviews_count, making it useful for finding products by keyword and then feeding slugs into get_product_details for deeper data.
The Product Hunt API is a managed, monitored endpoint for producthunt.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when producthunt.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official producthunt.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track which product categories dominate daily upvote charts by aggregating
topicsfields fromget_daily_leaderboard - Build a weekly digest of top-launched products by running
get_leaderboard_date_rangeover a seven-day window - Enrich a product database with maker profiles and screenshots using
get_product_detailsfor each known slug - Monitor launch momentum for a specific product by fetching its
upvotesacross multiple daily leaderboards - Find competing products in a niche by querying
search_productswith a keyword and comparingreviews_ratingvalues - Compile maker directories by collecting
makersarrays from product detail responses across a date range - Identify trending topic tags by aggregating the
topicsarray across leaderboard items over time
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Product Hunt have an official developer API?+
What does `get_leaderboard_date_range` return, and how does deduplication work?+
start_date and end_date, then deduplicates by slug so a product that appeared on multiple days appears only once. The returned items array is sorted by upvotes descending. Use the limit parameter to cap result size.Does `get_product_details` return individual review text or scores?+
reviews_count as an integer but does not expose individual review text, reviewer names, or per-review ratings. The API covers product metadata, maker info, media URLs, and aggregate counts. You can fork it on Parse and revise it to add an endpoint that fetches individual review content.Is there a way to retrieve comments or discussion threads for a launch?+
How far back does the daily leaderboard data go?+
get_daily_leaderboard and get_leaderboard_date_range endpoints accept any valid date, but data availability depends on whether Product Hunt's historical leaderboard pages exist for that date. Very old dates may return empty or partial results.