Extract Product Hunt launch, product, category, maker, ranking, and public product metadata as structured JSON for startup research, product discovery, market monitoring, AI workflows, and commercial-use evaluation.
Structured output
Use Crawlora's Product Hunt Scraper API to collect structured public launch, product, maker, category, and ranking data without maintaining your own parser, endpoint-specific extraction logic, retries, or response normalization layer. The endpoints support developer workflows for startup analysts, SaaS teams, AI agents, and data teams.
Startup workflows
Crawlora helps teams monitor daily launches, discover AI, SaaS, productivity, and developer-tool startups, enrich startup databases, track competitor launches, analyze categories, and feed AI agents with fresh product discovery data.
Product Hunt research workflowsRequest schema
These parameters come from the active Search for products, users, or launches on Product Hunt catalog entry.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| query | string | Yes | Search keywords | - |
| type | string | No | Result type: **product** (default), **user**, or **launch** | - |
| page | integer | No | Page number (1-based) | - |
| featured | boolean | No | Launch search only: featured launches only | - |
| topics | string | No | Launch search only: comma-separated topic slugs | - |
Example JSON
This example is rendered from the active endpoint catalog so the page stays aligned with Docs and Playground.
{
"code": 200,
"msg": "OK",
"data": {
"edges": [
{
"node": {
"id": "1050265",
"name": "HeroUI Chat",
"tagline": "Build and ship beautiful UIs with AI and HeroUI",
"slug": "heroui-chat",
"reviewsRating": 4.8,
"reviewsCount": 5
}
}
],
"pageInfo": {
"page": 1,
"hasPreviousPage": false,
"hasNextPage": true
},
"pagesCount": 394
}
}Endpoint catalog
/producthunt/searchPerforms a full-text Product Hunt search and returns matching products, users, or launches.
Response notes
- The `data` shape depends on `type`: `product` returns product edges, `user` returns user edges, and `launch` returns post edges plus topic aggregations. Example response: ```json { "code": 200, "msg": "OK", "data": { "edges": [ { "node": { "id": "1050265", "name": "HeroUI Chat", "tagline": "Build and ship beautiful UIs with AI and HeroUI", "slug": "heroui-chat", "reviewsRating": 4.8, "reviewsCount": 5 } } ], "pageInfo": { "page": 1, "hasPreviousPage": false, "hasNextPage": true }, "pagesCount": 394 } } ```
MCP tool producthunt_search
/producthunt/product/{id}Returns the core Product Hunt product details.
MCP tool producthunt_product
/producthunt/product/{id}/launchesReturns paginated launch posts for a Product Hunt product using Product Hunt's ProductPageLaunches GraphQL operation.
Response notes
- Returns `404` when Product Hunt does not return a product for the slug. - Returns `503` when Product Hunt omits the launches/posts connection or returns a blocked/malformed upstream payload.
MCP tool producthunt_launches
/producthunt/leaderboardFetches Product Hunt leaderboard data for daily, weekly, monthly, or yearly scopes via Product Hunt GraphQL.
Response notes
- The result is the first page Product Hunt server-renders for the requested scope/date (`scope`, `date`/`year`/`month`/`day`/`week`). `has_next_page` and `end_cursor` reflect whether Product Hunt has further pages. - Cursor pagination is currently unavailable: Product Hunt's GraphQL endpoint runs Automatic Persisted Queries in safelist mode and cannot be replayed for subsequent pages, so a request with a non-empty `cursor` returns an upstream error. Only the first page is served. - `featured` and `order` are accepted for compatibility but reflect Product Hunt's default leaderboard view for the requested scope/date. Example response: ```json { "code": 200, "msg": "OK", "data": { "scope": "daily", "featured": true, "order": "DAILY_RANK", "year": 2026, "month": 4, "day": 27, "week": 18, "connection": "homefeedItems", "has_next_page": false, "items": [ { "type": "post", "post": { "id": "1101061", "name": "Kitty Points Leaderboard", "slug": "kitty-points-leaderboard", "tagline": "Find interesting community members and see how you stack up", "latest_score": 140, "daily_rank": 3, "weekly_rank": 9, "comments_count": 18, "product": { "id": "112572", "slug": "producthunt", "name": "Product Hunt" } } } ] } } ```
MCP tool producthunt_leaderboard
/producthunt/category/{slug}Returns the category page payload for a Product Hunt category slug.
MCP tool producthunt_category
/producthunt/category/{slug}/productsReturns the products in a Product Hunt category (now backed by Product Hunt topics), cursor-paginated. Pass the `cursor` from a previous response's `end_cursor` to page; `page_size` controls the batch size. `page`, `featured_only`, `order` and `tags` are accepted for compatibility but no longer affect the result.
MCP tool producthunt_category_products
/producthunt/product/{id}/makersReturns maker items for a Product Hunt product.
Response notes
- Pass the returned `cursor` value from a previous response to continue pagination. Example response: ```json { "code": 200, "msg": "OK", "data": { "product_id": "1191613", "slug": "clico", "connection": "makers", "total_count": 3, "end_cursor": "Mw", "has_next_page": false } } ```
MCP tool producthunt_makers
/producthunt/product/{id}/reviewsReturns detailed review items for a Product Hunt product.
MCP tool producthunt_reviews
/producthunt/product/{id}/aboutReturns the richer Product Hunt about-page payload, including launch, forum, review tags, and media data.
MCP tool producthunt_about
/producthunt/product/{id}/alternativesReturns paginated alternatives, tags, and related discussions for a Product Hunt product.
Response notes
- Pass the returned `cursor` value from a previous response to continue pagination. Example response: ```json { "code": 200, "msg": "OK", "data": { "product_id": "1191613", "slug": "clico", "name": "Clico", "followers_count": 577, "categories": [ "Writing assistants" ], "alternative_tags": [ { "name": "chrome extension", "count": 24 } ] } } ```
MCP tool producthunt_alternatives
/producthunt/product/{id}/customersReturns paginated customer products for a Product Hunt product using Product Hunt's ProductCustomersPage GraphQL operation.
Response notes
- Returns `404` when Product Hunt does not return a product for the slug. - Returns `503` when Product Hunt omits the customers/products connection or returns a blocked/malformed upstream payload.
MCP tool producthunt_customers
Managed execution
Crawlora wraps Product Hunt endpoint-specific request handling, parser maintenance, response normalization, documented errors, Playground-tested examples, and credit-based usage behind a stable API surface.
Endpoint-specific request handling for Product Hunt search, product, launch, category, maker, and review pages
Parser maintenance and normalized JSON responses for supported public Product Hunt pages
Proxy-aware collection and retry-aware execution where supported
Documented error behavior instead of silently returning broken HTML
Docs and Playground examples generated from the active catalog
Credit-based billing tied to documented endpoint costs
Build or buy
Use this comparison to decide whether to maintain scraping infrastructure internally or call a managed endpoint.
| Requirement | Building internally | Crawlora |
|---|---|---|
| Parser maintenance | Maintain selectors and response parsing as Product Hunt pages change. | Use endpoint-specific parsers maintained behind the Crawlora API. |
| Structured response schema | Design and keep your own JSON model consistent. | Use documented response schemas generated from the active catalog. |
| Endpoint documentation | Write and maintain internal API docs. | Use Crawlora Docs pages for each active Product Hunt endpoint. |
| Playground testing | Build a test console for developers. | Run Product Hunt endpoints in Playground before integrating. |
| Retries and error classification | Classify empty pages, upstream failures, and parser drift yourself. | Receive documented errors for unusable upstream responses. |
| Usage billing | Build metering and plan enforcement. | Use credit-based usage and plan limits. |
| Monitoring | Instrument request volume and failures from scratch. | Use Crawlora's documented status and usage workflows. |
| Scaling | Operate queues, proxies, and execution infrastructure. | Call managed scraping endpoints for supported public pages. |
Crawlora is not the official Product Hunt API. Crawlora provides structured public web data extraction endpoints for supported Product Hunt pages. Customers are responsible for ensuring their use complies with applicable laws, third-party rights, platform terms, and Crawlora terms. Commercial use depends on your use case, applicable law, third-party rights, and platform terms. Crawlora provides tooling for structured public web data extraction, but customers are responsible for using the data lawfully and responsibly.
Related APIs
Connect this endpoint with adjacent Crawlora search, monitoring, docs, and pricing pages.
Pair startup discovery with public finance and market research workflows.
OpenCollect public review signals for company and product reputation research.
OpenResearch app metadata, ratings, reviews, and rankings.
OpenAdd Android app metadata and review workflows.
OpenCheck what to review before using Product Hunt data commercially.
OpenReview plans, credits, limits, and usage options.
OpenBrowse all active Crawlora API endpoints.
OpenHow to scrape Product Hunt
Crawlora's Product Hunt endpoints are GETs that read public Product Hunt pages and its public GraphQL operations: /producthunt/search for products, users or launches by query, /producthunt/leaderboard for daily, weekly, monthly or yearly rankings, /producthunt/category/{slug} and /producthunt/category/{slug}/products (cursor-paginated, now backed by topics), and per product /producthunt/product/{id} plus its about, launches, makers, reviews, alternatives and customers routes. The product comments route was deprecated on May 1, 2026 and is no longer available.
GET /producthunt/search?query=<name>&type=<products, users or launches> returns matches with their ids and slugs; add featured and topics filters to narrow. /producthunt/leaderboard?scope=daily&date=<YYYY-MM-DD> (or weekly, monthly, yearly) returns that period's ranked launches.
GET /producthunt/product/{id} for core details, /producthunt/product/{id}/about for the richer about-page payload (launch, forum, review tags, media), /producthunt/product/{id}/launches for its launch history, /producthunt/product/{id}/makers for the team and /producthunt/product/{id}/reviews for detailed reviews.
GET /producthunt/product/{id}/alternatives for alternatives, tags and related discussions, and /producthunt/product/{id}/customers for products that list it as a customer. /producthunt/category/{slug}/products walks a topic with cursor and page_size, with featured_only and order filters.
Key records on the product, not the launch: one product accumulates launches over time. Store upvotes and comment counts with a fetched-at timestamp, because launch-day numbers move during the day.
FAQ
Answers for developers evaluating Crawlora for supported public Product Hunt launch and product pages.
Yes. Crawlora provides Product Hunt endpoints for supported public Product Hunt pages and returns structured JSON through documented API routes. It works as a Product Hunt scraper API (also written ProductHunt scraper API) for launches, products, makers, categories, and rankings.
No. Crawlora is not the official Product Hunt API. Crawlora provides structured public web data extraction endpoints for supported public Product Hunt pages.
The official Product Hunt API is a GraphQL API that requires an OAuth developer token from the Product Hunt dashboard. Crawlora's Product Hunt endpoints need only your Crawlora API key (sent as the x-api-key header) — there is no separate Product Hunt API key, token, or app approval to provision.
The active catalog includes Product Hunt search, product details, product about pages, alternatives, customers, launches, makers, detailed reviews, categories, category products, and leaderboards where supported.
Yes. Product Hunt data can support startup research, launch monitoring, product discovery, category analysis, and internal research dashboards when your use complies with applicable laws, third-party rights, platform terms, and Crawlora terms.
Yes. Product Hunt endpoints return normalized JSON responses with documented request parameters, response schemas, examples, and Playground-tested calls where available.
Crawlora detects unusable upstream responses and returns documented errors instead of silently returning broken HTML. Customers should handle errors, retries, and upstream availability changes in their integrations.
Commercial use depends on your use case, applicable law, third-party rights, and platform terms. Crawlora provides tooling for structured public web data extraction, but customers are responsible for using the data lawfully and responsibly.
As of 2026, Crawlora does not grant Product Hunt's rights and is not the official Product Hunt API, so commercial-use terms come from three places: Product Hunt's own platform terms and API/licensing policy, applicable law and third-party rights in your jurisdiction, and the Crawlora terms that govern how you may use the structured data Crawlora returns. Review all three before using Product Hunt data in a commercial product, and treat platform terms as the controlling source for what Product Hunt itself permits. These terms can change, so re-check the current Product Hunt policy rather than relying on a cached summary.
Search with Crawlora's /producthunt/search endpoint or read a period's ranking from /producthunt/leaderboard, then GET /producthunt/product/{id} and its about, launches, makers, reviews, alternatives and customers routes. Category pages paginate with a cursor.
Yes, a GraphQL API that is OAuth-gated, rate-limited per application and subject to approval and terms constraints for many commercial uses. It is built for integrations rather than longitudinal research, which is why research teams read the public pages instead.
Yes. the /producthunt/product/{id}/launches endpoint returns the product's launch posts with cursor pagination, so a product that relaunched several times shows every launch.
No. The product comments route was deprecated on May 1, 2026 due to unstable upstream reliability and no longer returns data. Reviews, makers, launches and alternatives remain available.
Call the /producthunt/category/{slug}/products endpoint with page_size, then pass the response's end_cursor back as cursor to fetch the next batch; featured_only and order filter the set.
Guides
Read Crawlora guides and comparisons that use the Product Hunt API.
Get Product Hunt launch, product, and maker data in 2026 — the official GraphQL API, no-code tools, or one structured API — with real JSON examples.
Product Hunt trends, 2013–2026: we read every leaderboard. AI agents went from 0 to 9 of the annual Top 10 by 2025, and the trend rotates monthly, not yearly.
Using Product Hunt data commercially? See what Product Hunt's API docs and site terms actually permit, plus a pre-launch compliance checklist.
Test Product Hunt search in Playground, inspect the current response schema in Docs, and compare credit-based usage on the pricing page.