Product Hunt Daily Launches Scraper — Votes, Rankings, Topics & Makers (No API Key)

Track every product launch on Product Hunt — the world's largest community for discovering new tech products, with 4,000+ launches every month. Get votes, live score, daily / weekly / monthly rankings, topics, taglines, thumbnails, launch dates and makers in clean structured JSON, scraped straight from the public leaderboard and topic pages. No developer token, no OAuth, no login, no setup — with an optional official-API mode that unlocks full descriptions, media, reviews and comments.

🏆 Why this Product Hunt scraper?

17+ fields per launch · daily snapshots, date ranges & topic leaderboards · works out of the box with no API key · optional official GraphQL API for richer data · founder / maker lead-gen enrichment · export to JSON / CSV / Excel. The unofficial Product Hunt API alternative for market intelligence, trend detection, newsletters and founder outreach.

---

✨ What this Actor does / Key features

• 📅 Three scraping modes — a single day's launches (daily), a historical window (dateRange), or a topic/category leaderboard (topic).
• 🏆 Full ranking data — live votesCount, launch-day votes, plus dailyRank, weeklyRank and monthlyRank (#1 = Product of the Day).
• 🏷️ Topics & taglines — every launch's category tags and one-line pitch, ideal for classification and digests.
• 🖼️ Thumbnails & links — product thumbnail image URL and canonical Product Hunt product URL.
• 👤 Makers included — every enriched launch carries its makers' names, usernames, headlines and avatars, plus the full launch description, for founder lead generation.
• 🔀 Flexible sorting — order by votes/rank, newest, or featured date.
• 🔓 Zero-key engine — parses the React Server Component data embedded in Product Hunt's public HTML. Product Hunt serves a Cloudflare challenge to ordinary proxies, so the Actor passes it automatically through the Apify Unblocker proxy.
• 🔑 Optional official API — supply free Product Hunt credentials to switch to the GraphQL API v2 for website, media, reviewsCount, reviewsRating and full comments, with automatic fallback to the web scrape.
• 🛡️ Proxy support — the plain Apify Proxy by default; the Actor switches to the Apify Unblocker by itself when Product Hunt serves a Cloudflare challenge.

🚀 Quick start (3 steps)

1. Configure — pick a mode. The default daily needs nothing else to pull today's launches; or set a date, a dateFrom/dateTo window, or a topic slug.
2. Run — click Start. The Actor scrapes the leaderboard/topic pages and streams launches into your dataset.
3. Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API.

📥 Input

The Actor runs with zero configuration for today's launches. Everything else is optional.

Example — today's top launches (no key, zero setup)

{ "mode": "daily", "sortBy": "VOTES", "maxPosts": 100 }

Example — a specific day, enriched with makers (founder lead-gen)

{
  "mode": "daily",
  "date": "2026-07-05",
  "enrichDetails": true,
  "enrichLimit": 60
}

Example — a topic leaderboard (AI category intelligence)

{
  "mode": "topic",
  "topic": "artificial-intelligence",
  "sortBy": "VOTES",
  "maxPosts": 200
}

Example — a historical date range (longitudinal dataset)

{
  "mode": "dateRange",
  "dateFrom": "2026-06-01",
  "dateTo": "2026-06-30"
}

Field	Type	Description
mode	string	daily (one day), dateRange (multiple days) or topic (category leaderboard). Default daily.
date	string	Target date for daily mode (YYYY-MM-DD). Empty = today on Product Hunt's own (Pacific-time) clock.
dateFrom / dateTo	string	Start / end date for dateRange mode (YYYY-MM-DD).
topic	string	Topic slug for topic mode, e.g. artificial-intelligence, developer-tools, saas.
sortBy	string	VOTES (rank), NEWEST or FEATURED_AT. Default VOTES.
maxPosts	integer	Max launches to return. 0 = unlimited. Default 500.
enrichDetails	boolean	Obsolete — makers and the full description now always come with enrichment at no extra cost. Kept for backwards compatibility.
enrichLimit	integer	No-key mode: how many launches to enrich (votes + tagline come from this step). 0 = enrich all. Default 60.
scrapeComments	boolean	Official API only: include top comments per post. Default false.
maxComments	integer	Max comments per post (official API only). Default 20.
apiKey / apiSecret	string	Optional. Switches to the official GraphQL API for richer data.
accessToken	string	Optional. Pre-obtained Bearer token — use instead of key + secret.
proxyConfiguration	object	Proxy for the web scrape. Defaults to the plain Apify Proxy; the Actor switches to the Apify Unblocker automatically when Product Hunt serves a Cloudflare challenge.

Popular topic slugs: artificial-intelligence, developer-tools, productivity, marketing, design-tools, saas, no-code, open-source, fintech. Find a slug by opening any Product Hunt topic page and copying the path segment after /topics/.

📤 Output

One row per launch — 17+ fields, exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record (no-key mode):

{
  "id": "1149728",
  "name": "Elentaria",
  "slug": "elentaria",
  "tagline": "Your GTM: from diagnosis to execution",
  "url": "https://www.producthunt.com/products/elentaria",
  "votesCount": 576,
  "launchDayVotes": 544,
  "commentsCount": 97,
  "dailyRank": 1,
  "weeklyRank": 2,
  "monthlyRank": 2,
  "launchDate": "2026-07-05",
  "featuredAt": "2026-07-05T00:01:00-07:00",
  "thumbnailUrl": "https://ph-files.imgix.net/48d14be3-c76f-470b-a30d-be79b45c0f5f.jpeg",
  "topicNames": ["Sales", "Marketing"],
  "makerNames": ["Jane Doe"],
  "makerUsernames": ["janedoe"],
  "source": "web",
  "scrapedAt": "2026-07-06T12:00:00.000Z"
}

💡 Use cases

• Competitor & market intelligence — track what launches in your category every day.
• Trend detection — see which topics get the most traction this week or month.
• Newsletter & content curation — power a daily/weekly digest of the top launches.
• Founder lead generation — capture the makers behind every launch, with usernames and headlines.
• AI / LLM training data — high-quality product names, taglines and descriptions.
• Academic & longitudinal research — build one of the best datasets of tech launches over time via dateRange mode.

👥 Who uses it

Growth & market-intelligence teams · SaaS and AI founders watching their category · newsletter and media curators · VC and startup scouts sourcing fresh launches · sales/lead-gen teams targeting makers · researchers building product-launch datasets.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the launches you extract, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

Does this Product Hunt scraper need an API key or login? No. The default engine scrapes Product Hunt's public leaderboard and topic pages out of the box — no developer token, no OAuth, no login. You can optionally add a free API key only for richer maker/description/review fields.

Is scraping Product Hunt legal? The Actor collects only publicly available launch data from pages Product Hunt serves to everyone. You are responsible for using the output in line with Product Hunt's terms and applicable laws.

Do I need a proxy? The plain Apify Proxy is enabled by default, and the Actor switches to the Apify Unblocker by itself when Product Hunt serves a Cloudflare challenge — you do not need to pick a proxy group. Saved tasks that name a residential group keep working. You can override the proxy in the proxy settings.

How many launches can I scrape per run? A typical day's leaderboard carries 17 ranked launches, a topic page up to ~200, and a one-month dateRange roughly 500 launches (17 per day). Set maxPosts to 0 for unlimited.

How do I get makers and full descriptions without an API key? You already do — they come with the standard enrichment step, which visits each launch's own page. Use enrichLimit to control how many launches are enriched (default 60, 0 = all).

What extra data does the optional API mode add? When you supply credentials, the official GraphQL API v2 is used and adds website, media, reviewsCount, reviewsRating and full comments. If the API call fails, the Actor automatically falls back to the no-key web scrape.

Is this a Product Hunt API alternative?

Yes. The default engine scrapes the public leaderboard and topic pages with no developer token, so you get launches, votes, ranks and topics as a Product Hunt API alternative without OAuth setup.

Can I scrape Product Hunt without an API key or login?

Yes — no API key, no login, no developer account. It parses the public leaderboard pages out of the box; a free API key is optional and only adds richer maker/description fields.

How do I export Product Hunt launches to CSV or JSON?

Every run writes results to an Apify dataset you can download as CSV, JSON, Excel or XML — an easy Product Hunt data export for daily launches.

Can I extract Product Hunt data by topic or date range?

Yes. Use topic mode for category data (AI, Developer Tools, SaaS, etc.) or dateRange mode to pull a historical window of daily launches.

🔗 More social & product-data scrapers by logiover

Building a launch-and-community intelligence dataset? Pair Product Hunt with the rest of the social & product-data suite:

Source	Actor
💼 LinkedIn	LinkedIn Company Scraper · LinkedIn Top Content Scraper
👽 Reddit	Reddit Subreddit Scraper · Reddit Search Scraper
🧵 Threads	Threads Scraper
📌 Pinterest	Pinterest Scraper
💬 Q&A	Stack Exchange Questions Scraper · Hacker News Search Scraper
✍️ Writing	Dev.to Articles Scraper · Substack Newsletter Scraper
🎓 Community	Skool Scraper · Meetup Scraper
▶️ YouTube	YouTube Channel Scraper

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to snapshot Product Hunt's leaderboard every day and build a longitudinal launch dataset. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to auto-generate launch digests and founder lead lists.

⭐ Support & feedback

Found a bug or need an extra field? Open an issue on the Issues tab — response is usually fast. If this Actor saves you time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor extracts only publicly available launch data and is intended for legitimate research, analytics and lead-generation use. You are responsible for complying with Product Hunt's terms of service and any applicable local laws. Not affiliated with, endorsed by, or sponsored by Product Hunt.

---

How much Product Hunt Daily Launches data can you extract in one run?

A single run returned 17 products in about 60–70 seconds on the example input (with enrichment). That example is deliberately narrow; the result limit and the input list are both yours to widen. That is roughly 15 products a minute.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Product Hunt Daily Launches itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

Product Hunt Daily Launches scraping — frequently asked questions

Do I need a Product Hunt Daily Launches API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Product Hunt Daily Launches data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Product Hunt Daily Launches scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the products you care about really do change that fast.

How many products can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

Is scraping Product Hunt Daily Launches legal?

This Actor collects only information that Product Hunt Daily Launches publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Product Hunt Daily Launches blocks the run or changes its layout?

The first attempt uses your proxy route; if Product Hunt serves a Cloudflare challenge, the rest of the run goes through the Apify Unblocker and slow requests are re-sent in parallel. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

📝 Changelog

2026-11-01

• Fixed runs that finished successfully with zero results: Product Hunt now serves its pages behind a Cloudflare challenge, and the Actor gets past it by switching to the Apify Unblocker proxy automatically.
• A run that cannot fetch any Product Hunt page now fails with a clear message instead of ending as a successful run with an empty dataset, while a day that genuinely has no launches still ends successfully and says so.
• Pages and launch details are now fetched concurrently and stalled requests are re-sent in parallel, so a run stays within its time limit and one slow page no longer holds it up.
• The default proxy setting is now the plain Apify Proxy (the Actor picks the right route itself), and saved tasks that name a residential group keep working.
• Daily mode without a date now follows Product Hunt's own Pacific-time day, so it no longer asks for a day that has not started yet during the first hours of the UTC day.
• The fallback for a nearly empty leaderboard now fetches at most two popular topic pages, one at a time, instead of up to six.
• Custom proxy URLs entered in the proxy setting are now actually used.
• README refreshed: 2 links to renamed Actors updated, 1 link to retired Actors removed.

2026-10-15

• Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
• A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
• A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
• Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.

2026-09-24

Fixed the four columns that were always empty — description, makers, makerNames and makerUsernames.

• Enrichment was fetching the bare product page, /products/{product}. That URL carries the vote tally but renders the product's latest launch, not the one being scraped, and on established products it embeds no makers data at all — its user records there are forum commenters and reviewers. Enrichment now requests the canonical launch URL, /products/{product}?launch={postSlug}, which server-renders the same votes/rank/tagline data plus that launch's own makers list and description. Same number of requests, no extra cost. (/posts/{slug} is not used: it 308-redirects to the canonical URL and following that redirect from the platform trips Product Hunt's edge protection.)
• Makers and the description were additionally gated behind enrichDetails, which defaults to off — so even users who did get the right page saw empty columns. Both now come with the standard enrichment step. Measured on a live daily-leaderboard run of 17 launches: description 0% → 100%, and makers / makerNames / makerUsernames 0% → 94% (the one miss is a launch whose page carries no maker list). Overall cell fill on that run is 99.3%.
• Coverage note: makers are inlined on fresh launch pages. When the daily leaderboard is unavailable and the Actor falls back to topic pages, those return older, established launches whose pages often omit the maker strip, so expect lower maker coverage there. Rows beyond enrichLimit (default 60) are still returned but carry no enriched fields at all — raise it or set it to 0 if you need every row enriched.
• Descriptions no longer ship raw HTML entities (don't → don't).
• Removed a fallback that returned every user found on the page as a "maker" when no maker list could be located. On a product page that meant handing back seven random commenters as the founders of a product. Makers are now only the users Product Hunt explicitly declares as makers of that launch; if none can be read, the field is empty rather than wrong.
• enrichDetails is now obsolete in no-key mode and documented as such. It is still accepted so existing runs and saved tasks keep working unchanged.

2026-09-23

• Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
• Output verified on a live run: 25 columns returned, 84.0% of cells populated.
• Run reliability reviewed: 98.5% of public runs succeeded in the last 30 days.
• Input schema, output schema and pricing configuration reviewed.
• Noted that 4 column(s) came back empty in this sample (description, makers, makerNames, makerUsernames); these are under review.

2026-09-01

• Fixed a silent failure: when every page came back truncated or blocked, the run finished successfully with an empty dataset, which was indistinguishable from a day with no launches. The run now says so explicitly, names the cause, and tells you which proxy group works for Product Hunt.
• Verified end-to-end against live pages; unchanged output fields and types.

2026-08-11

• Maintenance release: refreshed the build and dependencies.
• Re-verified live execution, non-empty structured output and dataset field/type integrity.
• Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

2026-08-01

• Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
• Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.

2026-07-06

• ✨ README overhaul: richer output sample, ready-to-run example scenarios per mode, full field reference, social & product-data suite cross-links, and clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-15

• Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

2026-06-07

• Docs: added coverage for using this as a Product Hunt API alternative, scraping without an API key/login, and exporting daily launches to CSV/JSON.

2026-06-05

• 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
• ⚡ Stability & performance hardening; fresh rebuild.

2026-06-04

• Major: no API key required. Default engine now scrapes Product Hunt's public leaderboard / topic pages (name, tagline, votes, rank, topics, thumbnail, launch date) with zero setup. API key is now fully optional and only adds makers/description/comments. Added enrichDetails for no-key maker + description enrichment.

---

*Maintained: last verified 2026-11-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).