Hacker News still concentrates a kind of signal that social feeds dilute: Show HN launches, Ask HN tooling debates, monthly Who is Hiring threads, and comment threads that are more honest than most review sites. When people search for a "Hacker News API," they usually want one of three things — wire HN into a product request handler, run overnight batch dumps, or cobble public HN endpoints together themselves.

Those are different products. Mixing them up is how you end up with a fragile glue layer: ranked id lists with no titles attached, comment trees you walk node by node, search hits that do not match your story schema, and a favorites page that never showed up in the JSON APIs at all.

This is a coverage and ergonomics comparison for July 2026. Re-check each vendor's docs and pricing before you commit budget.

Social Fetch is my pick for sync REST over HN search, ranked feeds, stories, comment pages, user history, public favorites, and structured Who is Hiring rows — especially if you already normalize Reddit, X, or Web under the same key. Prefer DIY against HN's public read surfaces when HN is your only network and you want to own every hop. Prefer Apify when you need a custom crawl field nobody documents. Prefer raw browser stacks only when you need HTML or screenshots, not a profile of a story.

The short list

1. Social Fetch — sync REST for search, feeds, stories, comments, users, favorites, hiring
2. DIY on HN's public read APIs — assemble item, user, feed, and search clients yourself
3. Apify / custom actors — scheduled dumps and niche field extraction
4. API marketplaces — RapidAPI-style listings for weekend discovery
5. Generic proxy + browser stacks — raw page capture when you will parse yourself
6. HN-only niche APIs — smaller catalogs that only cover Hacker News

Full route list: Hacker News platform page. Hands-on walkthrough: How to scrape Hacker News data.

What teams actually buy an HN API for

Ignore "we support Hacker News" marketing grids. The jobs that show up in production tickets look like this:

If a provider cannot clear those rows, you will rebuild the missing pieces yourself — which is how "free official access" turns into a second product.

How I rank Hacker News data APIs

1. Assembled objects vs plumbing — do feeds return hydrated stories, or id lists you must fan out?
2. Search and story shape — can one parser handle hits and story gets, or do you maintain two models?
3. Comment pagination — busy threads need pages and cursors, not a single recursive dump that blows timeouts.
4. Hiring and favorites — these are the surfaces DIY most often skips; they are also high-signal.
5. Typed misses — lookupStatus and empty hits beat silent HTML.
6. Sync vs async — product handlers prefer one HTTP round trip; overnight dumps can live on actors.
7. Multi-platform tax — if Reddit already shares your envelope, does HN force a second client?
8. Compliance fit — public HN data under Y Combinator's terms; you own how you use it. I am not your lawyer.

Ranked picks

1. Social Fetch — HN under one marketplace key

Best for: product teams and agents that need search, digests, comment pages, author history, public favorites, and Who is Hiring beside other networks — without owning HN glue code.

Social Fetch exposes documented /v1/hackernews/** routes with the shared { data, meta } envelope — meta.requestId, meta.creditsCharged, and typed outcomes where routes expose lookupStatus. Authenticate with x-api-key. New accounts get 100 free credits. Each successful request or cursor page is credit-metered; confirm meta.creditsCharged.

What that buys in practice:

• Search with type, author, domain, URL, and minPoints filters for brand and launch monitors.
• Ranked feeds (top, new, best, ask, show, jobs) with hydrated items, not id-only lists.
• Story + comment pages for discussion jobs; polymorphic item get when the id type is unknown.
• User card + submissions / comments / public favorites for author analysis.
• Who is Hiring as structured rows with best-effort company / role / location fields and the full plain-text body as source of truth.

Coverage is public data. Private favorites return lookupStatus: private_or_unavailable. Upvoted pages are not supported.

Pricing: Free (100 credits) → packs on pricing.

Verdict: Default when HN is one surface in a multi-platform product, or when hiring / favorites / sync REST matter more than owning every public endpoint yourself.

Hub: /platforms/hackernews. Guide: How to scrape Hacker News data.

2. DIY on HN's public read APIs

Best for: HN-only scripts where you want first-party public JSON and will own assembly, retries, and schema glue.

Hacker News publishes public read surfaces for items, users, and ranked feed id lists, plus a separate public search surface. That stack is genuinely useful — and genuinely incomplete as a product API. Feed endpoints give you ids; you hydrate each item. Comment threads are trees you walk. Search hits rarely match your story object 1:1. Public favorites live on HTML pages, not the same JSON paths as items. Who is Hiring is a monthly comment thread you have to discover and parse.

DIY wins when HN is the only network, volume is modest, and a staff engineer already knows the quirks. It loses when a customer-facing feature needs one error shape, one credit meter, and the same parser you use for Reddit next quarter.

Verdict: Keep it for internal scripts. Prefer a managed API when customers wait on your HTTP response or when hiring / favorites are part of the job.

3. Apify — actors for custom and batch work

Best for: scheduled dumps, niche HTML fields, and scrapers you want to configure as Actors rather than maintain as a fleet of browsers.

Apify hosts HN scrapers that start a run, poll, and download a dataset. Schemas differ by actor author. Billing mixes platform subscription, compute, and per-event fees; monthly plan credits expire. Model the listing you will actually run.

Marketplace breadth helps when no managed REST route exposes the field you need. Sync product UIs that need a single HTTP round trip fit poorly. See Social Fetch vs Apify.

Verdict: Right for batch and custom scrapes. Wrong as your only integration if you want typed search + comments in a request handler.

4. API marketplaces — browse, then graduate

Best for: finding a niche HN endpoint over a weekend without signing an enterprise contract.

RapidAPI-style marketplaces aggregate third-party HN scrapers. One billing UI, many publishers, no shared schema. Fine for disposable prototypes. Weak for production monitoring: pagination, freshness, and empty-result behavior vary by publisher. Adding Reddit or Truth Social beside HN means more listings and more adapters. Longer take: Social Fetch vs RapidAPI.

Verdict: Exploration only. Prefer a first-party sync API when HN sits in a product feature.

5. Generic proxy and browser stacks

Best for: raw HTML, screenshots, or one-off captures you will parse yourself.

Proxy and browser products are infrastructure. They do not give you a Who is Hiring row with lookupStatus. Buy them when you need capture; buy a data API when you need query → JSON.

6. HN-only niche APIs

Best for: teams that only ever need Hacker News and prefer a small catalog over a multi-network marketplace.

A few vendors sell HN-only REST catalogs (search, lists, items, users). They can be fine if HN is the entire product. They leave you with a second vendor the day you add Reddit brand mentions or Web extraction. Compare field coverage carefully — many skip favorites and structured hiring.

Verdict: Acceptable for HN-only tools. Prefer Social Fetch when the roadmap already includes other networks.

DIY public HN APIs vs a managed product API

Which option fits which job

Questions before you buy

1. Do you need assembled stories, or are bare ids enough? Digests need hydration.
2. Is search part of the job? Many DIY stacks under-build search filters.
3. Will HN sit beside Reddit or Web? Prefer one schema if yes.
4. Sync or batch? Product handlers prefer sync.
5. Do credits expire? Spiky research sprints hate monthly resets.
6. Do you need hiring or favorites? Ask vendors explicitly — those are the common gaps.

Frequently asked questions

Is there a Hacker News API?

Yes. Hacker News publishes public read APIs for items, users, and feeds, plus a public search surface. Social Fetch provides a managed catalog under /v1/hackernews for search, feeds, stories, comments, users, favorites, and hiring. Hub: /platforms/hackernews.

How do I use Hacker News data in a product?

Call typed REST routes (or MCP tools), branch on lookupStatus where present, and store meta.requestId. Step-by-step: How to scrape Hacker News data.

Does Social Fetch require a Hacker News account?

No. You need a Social Fetch API key. Coverage is public HN data only.

Can I get a user's favorites?

Yes for public favorites via GET /v1/hackernews/users/{username}/favorites. Private favorites return lookupStatus: private_or_unavailable. Upvoted pages are not supported.

Official HN APIs vs a Hacker News data API — which should I use?

Use HN's public read APIs when you want to own every hop for an HN-only script. Use a managed data API when you need one key, one envelope, hydrated feeds, hiring helpers, and multi-network parity.

Smoke-test search in the playground, or start with 100 free credits on pricing. Broader roundup: Best social media scraping APIs in 2026.