Scraping API PricesHome / Cost to scrape / Product Hunt
Cost to scrape Product Hunt at 10K, 100K, and 1M
Published Product Hunt scraping rates, plan costs at three billable volumes, access facts, protections, and the official API option.
Access
Protections in the way
Terms
What you scrape moves the bill more than who you buy from. A target that forces JavaScript rendering or a residential exit multiplies the meter before any plan is chosen.
No vendor publishes a rate specific to this target. That is the finding.
It means the general meter applies: whatever the vendor charges for a page of this kind, with the rendering and proxy multipliers its own pricing page states. The market table prices exactly that.
Access fact, checked 2026-07-26: Product Hunt’s Terms require use of the service within the permissions and restrictions stated in its Terms and applicable product rules (Source).
Cost to scrape Product Hunt at 10K, 100K, and 1M table
| Route | 10K | 100K | 1M | Billing rule and source | Checked |
|---|---|---|---|---|---|
| Crawlbase: Product Hunt scrapers | Not published | Not published | Not published | Target endpoint is documented, but no target-specific public rate is in the record | 2026-07-26 |
| Product Hunt API 2.0 | Rate not in target record | Rate not in target record | Rate not in target record | No public fee is listed; fair-use rate limits apply and commercial use requires separate contact. | 2026-07-26 |
The comparison uses 10,000, 100,000, and 1,000,000 billable target calls or delivered results per month, calculated on 2026-07-26. It does not claim those calls all become useful rows. Credit, request, result, and search meters are passed through the dataset quote model, which selects the least expensive published self-service offer that covers each volume. A starting USD rate is shown as a lower bound because an unpublished minimum, tier, or contract can raise the invoice. Retries, pagination, duplicate outputs, taxes, and data licensing are outside these figures.
No public target price was found
The dataset contains no published surcharge or target-specific unit rate for Product Hunt. A vendor may document a dedicated endpoint without publishing what that endpoint costs at these volumes. Those rows remain “Not published” rather than borrowing a generic request price, because a generic price does not prove target support, residential routing, rendering, parser coverage, or the target-specific contract. The unknown is the answer until a first-party rate is published.
Rendering and access change the job
This record classifies Product Hunt as moderate and records rate limiting, bot detection and fingerprinting, a login wall, dynamic rendering. JavaScript rendering is required in the recorded profile, so a plain HTML request is not the same workload. Residential routing is not recorded as necessary, which keeps an unsupported premium-proxy assumption out of the calculation.
The requested fields, authentication state, response format, and rendering path must be fixed before a published unit rate becomes a usable estimate.
The official route is a separate product decision
Product Hunt API 2.0 is recorded as available. Requires an access token; public scope is read-only by default, and commercial use requires contacting Product Hunt. No public fee is listed; fair-use rate limits apply and commercial use requires separate contact. API 2.0 exposes public information under token and use restrictions, but commercial use needs separate contact. Source and access status checked 2026-07-26.
Endpoint evidence and the remaining unknown
The dataset confirms 1 dedicated endpoint or template. This proves named target support in the cited product documentation. It does not prove that each endpoint has a public target-specific price.
- Product Hunt scrapers is documented, while its target-specific price remains unpublished in this record.
What volume means for Product Hunt
One useful unit is one launch observation for a defined ranking window, with product details added only when required. Crawlbase documents Product Hunt daily and weekly leaderboard collection plus individual product collection, so a project that enriches every launch must count leaderboard results and product lookups as separate work (Crawlbase scraper catalogue, retrieved 2026-07-27).
The public Product Hunt API is GraphQL, but the reviewed documentation does not publish one stable page size or a target-wide continuation rule for all connections. The pagination multiplier therefore remains endpoint-specific and should be taken from the selected query’s schema and response rather than inferred from the rendered leaderboard (Product Hunt API v2 documentation, retrieved 2026-07-27).
The official API can answer public product, post, and related-object questions covered by its schema. Product Hunt requires commercial API users to contact it, and API objects do not reproduce the rendered leaderboard page, so access rights and ranking presentation remain separate decisions (Product Hunt API v2 documentation, retrieved 2026-07-27).
Evidence to check before buying
- Product Hunt provides a first-party GraphQL API for public information with access-token and fair-use controls api.producthunt.com.
- Crawlbase maintains a Product Hunt-specific scraper crawlbase.com.
- Confirm the exact entity and output unit, whether a page, search, result, record, or API object. Then multiply by pagination and refresh frequency before selecting a plan.
- Keep public and authenticated collection separate. The recorded login wall means credentials can change both the permitted route and the returned fields.