Hacker News Story, Comment & Karma Scraper
Pull Hacker News front-page, newest, best, Ask HN, Show HN, or job stories, look up specific items or user profiles, or run a full-text search across HN history. Filter by score, domain, date range, and comment count or author.
Input schema
Input fields, types, required flags, descriptions, defaults, and prefills come from the published definition. Prefill examples are distinct from defaults.
| Field | Type | Required | Description |
|---|---|---|---|
mode | string | required | What to scrape. Feeds walk the live Hacker News lists. `item` looks up specific IDs, `user` loads profiles, `search` queries Hacker News history, `frontPage` reads a historical day, and `whoIsHiring` parses monthly hiring threads. |
itemIds | array | optional | Hacker News item IDs to look up, as numbers or numeric strings. Stories, comments, jobs, polls, and poll options are all accepted. |
usernames | array | optional | Hacker News usernames whose profiles and, optionally, submissions you want. |
Show all input fields
| Field | Type | Required | Description |
|---|---|---|---|
mode | string | required | What to scrape. Feeds walk the live Hacker News lists. `item` looks up specific IDs, `user` loads profiles, `search` queries Hacker News history, `frontPage` reads a historical day, and `whoIsHiring` parses monthly hiring threads. |
itemIds | array | optional | Hacker News item IDs to look up, as numbers or numeric strings. Stories, comments, jobs, polls, and poll options are all accepted. |
usernames | array | optional | Hacker News usernames whose profiles and, optionally, submissions you want. |
searchQueries | array | optional | One or more keyword queries. Every query runs independently and the results are merged without duplicates. Leave empty to browse by tags, author, or story instead. |
searchSort | string | optional | `relevance` ranks by keyword match. `date` returns newest first and is more reproducible. |
contentTypes | array | optional | Which Hacker News record types search should return. Selecting several types returns any of them. `front_page` covers only the current front page. |
author | string | optional | Only return content written by this Hacker News username. |
storyId | string | optional | Only return content attached to this story ID. Useful with `contentTypes` set to `comment` to search inside one thread. |
exhaustiveSearch | boolean | optional | Hacker News search exposes at most 1,000 hits per query. When enabled, the actor splits the requested date range into smaller windows so deeper result sets can be collected. Relevance order then follows each date window rather than one global ranking. |
dateRangeFrom | string | optional | Drop items posted before this date (UTC, `YYYY-MM-DD`). Empty means no lower bound. |
dateRangeTo | string | optional | Drop items posted after this date (UTC, `YYYY-MM-DD`). Empty means no upper bound. |
minScore | integer | optional | Drop stories, jobs, and polls below this point score. Comments are unaffected because Hacker News does not publish comment scores. |
minCommentCount | integer | optional | Drop stories and polls with fewer than this many comments. |
domainAllowlist | array | optional | Keep only stories whose link host contains one of these text fragments. For example, `github.com` or `arxiv.org`. |
domainBlocklist | array | optional | Drop stories whose link host contains one of these text fragments. For example, `twitter.com` or `x.com`. |
excludeDeadOrDeleted | boolean | optional | Drop items marked dead or deleted by Hacker News. Turning this off uses the slower exact comment path so those records can be included. |
commentAuthorFilter | array | optional | Only keep comments written by these usernames. Matching is case-insensitive and accepts partial names. |
commentSort | string | optional | `rank` keeps Hacker News display order. `newest` orders sibling replies newest first. |
maxComments | integer | optional | How many comments to collect for each story. 0 skips comment collection. This is applied after a story passes your filters. |
maxDepth | integer | optional | Deepest reply level to keep when comments are collected. Root comments are depth 0. |
enableCommentHierarchy | boolean | optional | When true, each story carries a nested `comments` tree. When false, comments are separate rows and never contain duplicate reply rows. |
includeSubmissions | boolean | optional | For mode `user`, also emit the user's recent stories and comments as normal records after the profile. |
submissionTypes | string | optional | Which submissions to emit when `includeSubmissions` is enabled. |
frontPageDate | string | optional | Historical day to read in mode `frontPage`, as `YYYY-MM-DD`. Empty uses yesterday (UTC). |
hiringMonths | integer | optional | How many recent monthly Who is hiring? threads to parse. Ignored when specific thread IDs are supplied. |
hiringThreadIds | array | optional | Specific Who is hiring? thread IDs to parse. Overrides the automatic monthly selection. |
hiringKeywords | array | optional | Keep only job posts whose text, company, role, location, or tech stack contains one of these terms. |
remoteOnly | boolean | optional | Keep only hiring posts that explicitly mention remote work. |
maxItems | integer | optional | Hard cap on emitted records across all types. Nested comments also count toward this cap. |
includeAuthorProfiles | boolean | optional | Add `authorKarma` and `authorCreatedAt` to stories and comments. This costs one extra lookup per unique author. |
startUrls | array | optional | Hacker News links to read directly: item, user, historical front-page, and hiring-thread URLs. IDs and URLs are merged with the mode-specific lists. |
Download the published input schema
View complete JSON
{
"description": "Choose what to collect from Hacker News: live feeds, historical front pages, search results, specific items or users, or the monthly Who is hiring? threads.",
"properties": {
"author": {
"description": "Only return content written by this Hacker News username.",
"editor": "textfield",
"title": "Author (mode=search)",
"type": "string"
},
"commentAuthorFilter": {
"default": [],
"description": "Only keep comments written by these usernames. Matching is case-insensitive and accepts partial names.",
"editor": "stringList",
"prefill": [],
"title": "Comment author filter",
"type": "array"
},
"commentSort": {
"default": "rank",
"description": "`rank` keeps Hacker News display order. `newest` orders sibling replies newest first.",
"editor": "select",
"enum": [
"rank",
"newest"
],
"enumTitles": [
"Hacker News rank",
"Newest first"
],
"prefill": "rank",
"title": "Comment order",
"type": "string"
},
"contentTypes": {
"default": [
"story"
],
"description": "Which Hacker News record types search should return. Selecting several types returns any of them. `front_page` covers only the current front page.",
"editor": "select",
"items": {
"enum": [
"story",
"comment",
"poll",
"pollopt",
"job",
"show_hn",
"ask_hn",
"front_page"
],
"enumTitles": [
"Stories",
"Comments",
"Polls",
"Poll options",
"Jobs",
"Show HN",
"Ask HN",
"Current front page"
],
"type": "string"
},
"prefill": [
"story"
],
"title": "Search content types",
"type": "array"
},
"dateRangeFrom": {
"description": "Drop items posted before this date (UTC, `YYYY-MM-DD`). Empty means no lower bound.",
"editor": "textfield",
"title": "Date range from",
"type": "string"
},
"dateRangeTo": {
"description": "Drop items posted after this date (UTC, `YYYY-MM-DD`). Empty means no upper bound.",
"editor": "textfield",
"title": "Date range to",
"type": "string"
},
"domainAllowlist": {
"default": [],
"description": "Keep only stories whose link host contains one of these text fragments. For example, `github.com` or `arxiv.org`.",
"editor": "stringList",
"prefill": [],
"title": "Domain allowlist",
"type": "array"
},
"domainBlocklist": {
"default": [],
"description": "Drop stories whose link host contains one of these text fragments. For example, `twitter.com` or `x.com`.",
"editor": "stringList",
"prefill": [],
"title": "Domain blocklist",
"type": "array"
},
"enableCommentHierarchy": {
"default": false,
"description": "When true, each story carries a nested `comments` tree. When false, comments are separate rows and never contain duplicate reply rows.",
"prefill": false,
"title": "Nest comment replies",
"type": "boolean"
},
"excludeDeadOrDeleted": {
"default": true,
"description": "Drop items marked dead or deleted by Hacker News. Turning this off uses the slower exact comment path so those records can be included.",
"prefill": true,
"title": "Exclude dead or deleted content",
"type": "boolean"
},
"exhaustiveSearch": {
"default": false,
"description": "Hacker News search exposes at most 1,000 hits per query. When enabled, the actor splits the requested date range into smaller windows so deeper result sets can be collected. Relevance order then follows each date window rather than one global ranking.",
"prefill": false,
"title": "Search past 1,000 results",
"type": "boolean"
},
"frontPageDate": {
"description": "Historical day to read in mode `frontPage`, as `YYYY-MM-DD`. Empty uses yesterday (UTC).",
"editor": "textfield",
"title": "Front page date",
"type": "string"
},
"hiringKeywords": {
"default": [],
"description": "Keep only job posts whose text, company, role, location, or tech stack contains one of these terms.",
"editor": "stringList",
"prefill": [],
"title": "Hiring keywords",
"type": "array"
},
"hiringMonths": {
"default": 1,
"description": "How many recent monthly Who is hiring? threads to parse. Ignored when specific thread IDs are supplied.",
"maximum": 12,
"minimum": 1,
"prefill": 1,
"title": "Hiring months",
"type": "integer"
},
"hiringThreadIds": {
"default": [],
"description": "Specific Who is hiring? thread IDs to parse. Overrides the automatic monthly selection.",
"editor": "stringList",
"prefill": [],
"title": "Hiring thread IDs",
"type": "array"
},
"includeAuthorProfiles": {
"default": false,
"description": "Add `authorKarma` and `authorCreatedAt` to stories and comments. This costs one extra lookup per unique author.",
"prefill": false,
"title": "Add author karma",
"type": "boolean"
},
"includeSubmissions": {
"default": false,
"description": "For mode `user`, also emit the user's recent stories and comments as normal records after the profile.",
"prefill": false,
"title": "Include user submissions",
"type": "boolean"
},
"itemIds": {
"default": [],
"description": "Hacker News item IDs to look up, as numbers or numeric strings. Stories, comments, jobs, polls, and poll options are all accepted.",
"editor": "stringList",
"prefill": [],
"title": "Item IDs (mode=item)",
"type": "array"
},
"maxComments": {
"default": 0,
"description": "How many comments to collect for each story. 0 skips comment collection. This is applied after a story passes your filters.",
"maximum": 5000,
"minimum": 0,
"prefill": 0,
"title": "Comments per story",
"type": "integer"
},
"maxDepth": {
"default": 5,
"description": "Deepest reply level to keep when comments are collected. Root comments are depth 0.",
"maximum": 20,
"minimum": 0,
"prefill": 5,
"title": "Maximum reply depth",
"type": "integer"
},
"maxItems": {
"default": 50,
"description": "Hard cap on emitted records across all types. Nested comments also count toward this cap.",
"maximum": 5000,
"minimum": 1,
"prefill": 20,
"title": "Maximum records",
"type": "integer"
},
"minCommentCount": {
"description": "Drop stories and polls with fewer than this many comments.",
"maximum": 1000000,
"minimum": 0,
"title": "Minimum comment count",
"type": "integer"
},
"minScore": {
"description": "Drop stories, jobs, and polls below this point score. Comments are unaffected because Hacker News does not publish comment scores.",
"maximum": 1000000,
"minimum": 0,
"title": "Minimum points",
"type": "integer"
},
"mode": {
"default": "topStories",
"description": "What to scrape. Feeds walk the live Hacker News lists. `item` looks up specific IDs, `user` loads profiles, `search` queries Hacker News history, `frontPage` reads a historical day, and `whoIsHiring` parses monthly hiring threads.",
"editor": "select",
"enum": [
"topStories",
"newStories",
"bestStories",
"askStories",
"showStories",
"jobStories",
"item",
"user",
"search",
"frontPage",
"whoIsHiring"
],
"enumTitles": [
"Top stories",
"New stories",
"Best stories",
"Ask HN",
"Show HN",
"Jobs",
"Items by ID",
"User profiles",
"Search",
"Historical front page",
"Who is hiring?"
],
"prefill": "topStories",
"title": "Mode",
"type": "string"
},
"remoteOnly": {
"default": false,
"description": "Keep only hiring posts that explicitly mention remote work.",
"prefill": false,
"title": "Remote jobs only",
"type": "boolean"
},
"searchQueries": {
"default": [],
"description": "One or more keyword queries. Every query runs independently and the results are merged without duplicates. Leave empty to browse by tags, author, or story instead.",
"editor": "stringList",
"prefill": [],
"title": "Search queries (mode=search)",
"type": "array"
},
"searchSort": {
"default": "relevance",
"description": "`relevance` ranks by keyword match. `date` returns newest first and is more reproducible.",
"editor": "select",
"enum": [
"relevance",
"date"
],
"enumTitles": [
"Most relevant",
"Newest first"
],
"prefill": "relevance",
"title": "Search order",
"type": "string"
},
"startUrls": {
"default": [],
"description": "Hacker News links to read directly: item, user, historical front-page, and hiring-thread URLs. IDs and URLs are merged with the mode-specific lists.",
"editor": "stringList",
"prefill": [],
"title": "Start URLs",
"type": "array"
},
"storyId": {
"description": "Only return content attached to this story ID. Useful with `contentTypes` set to `comment` to search inside one thread.",
"editor": "textfield",
"title": "Story ID (mode=search)",
"type": "string"
},
"submissionTypes": {
"default": "all",
"description": "Which submissions to emit when `includeSubmissions` is enabled.",
"editor": "select",
"enum": [
"all",
"story",
"comment"
],
"enumTitles": [
"Stories and comments",
"Stories only",
"Comments only"
],
"prefill": "all",
"title": "User submission types",
"type": "string"
},
"usernames": {
"default": [],
"description": "Hacker News usernames whose profiles and, optionally, submissions you want.",
"editor": "stringList",
"prefill": [],
"title": "Usernames (mode=user)",
"type": "array"
}
},
"required": [
"mode"
],
"schemaVersion": 1,
"title": "Hacker News Scraper Input",
"type": "object"
}
Output schema
Published result links and storage locations. This schema is not an exhaustive contract for every field in a dataset record.
| Field | Type | Required | Description |
|---|---|---|---|
items | string | optional | Dataset containing every scraped record. `recordType` identifies stories, comments, users, poll options, and hiring posts. Story rows include id, title, url, domain, score, author, numComments, rank, timestamps, text, pollOptions, and optional nested comments. Comment rows include id, storyId, parentId, depth, author, text, and story context. User rows include karma, account age, about text, and submission counts. |
Download the published output schema
View complete JSON
{
"actorOutputSchemaVersion": 1,
"description": "Stories, comments, jobs, polls, poll options, user profiles, and parsed Who is hiring? posts from Hacker News.",
"properties": {
"items": {
"description": "Dataset containing every scraped record. `recordType` identifies stories, comments, users, poll options, and hiring posts. Story rows include id, title, url, domain, score, author, numComments, rank, timestamps, text, pollOptions, and optional nested comments. Comment rows include id, storyId, parentId, depth, author, text, and story context. User rows include karma, account age, about text, and submission counts.",
"template": "{{links.apiDefaultDatasetUrl}}/items",
"title": "Hacker News records",
"type": "string"
}
},
"title": "Hacker News Archive: Stories, Comments & Hiring Output"
}
Dataset schema
Published dataset views and any declared field definitions. A view can select only a subset of the returned record fields.
Download the published dataset schema
View complete JSON
{
"actorSpecification": 1,
"views": {
"overview": {
"display": {
"component": "table",
"properties": {}
},
"title": "Hacker News",
"transformation": {
"fields": [
"recordType",
"title",
"company",
"role",
"url",
"score",
"author",
"numComments",
"createdAt",
"domain",
"frontPageDate"
]
}
}
}
}
Key-value schema
Published key-value store definitions, when provided by this build.
This definition is not present in the default published build. See the published README for available documentation.
Published README
Read the full published documentation
Hacker News Archive: Stories, Comments & Hiring
Hacker News is a living archive of technology discussion: front-page links, Ask HN and Show HN threads, job ads, polls, user karma, and years of comments. This actor collects all of it from the public Hacker News surfaces — live feeds, keyword search, historical front pages, individual items, user profiles, and the monthly “Who is hiring?” threads. No login, cookies, API key, or proxy setup is needed.
What it does
- 11 modes — six live feeds, item lookup, user profiles, keyword search, historical front pages, and monthly hiring threads.
- Complete comment trees — flat rows or nested
comments, with no duplicated replies and a correctmaxItemscap. - Deep search — relevance or newest-first ordering, tags, author, story, date range, points, and comment filters.
- Search past 1,000 results — adaptive date-window splitting keeps collecting when a query is larger than the search API’s per-query ceiling.
- Typed records — stories, comments, jobs, polls with vote options, poll options, user profiles, and parsed job postings.
- Historical front pages — read any day back to 2007 with its original ranking, score, author, and comment count.
Services
The actor reads three public Hacker News services:
| Service | What it provides |
|---|---|
| Firebase Hacker News API | Live feeds, individual items, user profiles, scores, comment counts, and exact deleted/dead flags |
| Algolia Hacker News Search | Keyword search, date ordering, tag and author filters, and fast comment-tree reads |
| Hacker News HTML | Historical /front?day= pages and their original story rankings |
All three are reachable without credentials.
How it works
Pick a mode and the actor chooses the right source for it:
- Feeds read the complete live list for the chosen section, then fetch item details and apply your filters. It keeps walking until the feed ends or
maxItemsis reached, so filtered-out stories do not silently shorten the result. - Search sends your query, tags, author, story, and date range to Hacker News search. With
exhaustiveSearchenabled it splits the date range whenever a window would exceed 1,000 hits, then merges the windows without duplicates. - Comments use the fast threaded read first. When a thread is missing live replies, the actor checks the thread’s comment search and merges the gap. Asking for dead or deleted content switches to the exact live item walk.
- Historical front pages read page after page of the chosen day, then deduplicate stories that appear twice.
- Who is hiring? finds the requested number of monthly threads, reads their top-level posts, and extracts the common hiring fields without inventing missing details.
Every mode is filter-aware: a story is checked before its comments are fetched, so filtered-out stories cost nothing extra.
Input
| Field | Type | Default | Description |
|---|---|---|---|
mode |
string | topStories |
topStories / newStories / bestStories / askStories / showStories / jobStories / item / user / search / frontPage / whoIsHiring |
itemIds |
array | [] |
Item IDs for mode=item |
usernames |
array | [] |
Usernames for mode=user |
searchQueries |
array | [] |
Keywords for mode=search; several queries are merged |
searchSort |
string | relevance |
relevance or date |
contentTypes |
array | ["story"] |
story, comment, poll, pollopt, job, show_hn, ask_hn, front_page |
author |
string | – | Restrict search to one username |
storyId |
string | – | Restrict search to one story |
exhaustiveSearch |
boolean | false |
Date-slice past the 1,000-hit search ceiling |
dateRangeFrom |
string | – | Earliest date (YYYY-MM-DD, UTC) |
dateRangeTo |
string | – | Latest date (YYYY-MM-DD, UTC) |
minScore |
integer | – | Minimum points for stories, jobs, and polls |
minCommentCount |
integer | – | Minimum comment count for stories and polls |
domainAllowlist |
array | [] |
Keep only these link-host fragments |
domainBlocklist |
array | [] |
Drop these link-host fragments |
excludeDeadOrDeleted |
boolean | true |
Drop dead/deleted items |
commentAuthorFilter |
array | [] |
Keep only comments by these authors |
commentSort |
string | rank |
rank or newest sibling order |
maxComments |
integer | 0 |
Comments collected per story; 0 skips comments |
maxDepth |
integer | 5 |
Maximum reply depth; roots are depth 0 |
enableCommentHierarchy |
boolean | false |
Nested comments instead of flat comment rows |
includeSubmissions |
boolean | false |
Also emit a user’s submissions |
submissionTypes |
string | all |
all, story, or comment |
frontPageDate |
string | – | Day for mode=frontPage; empty means yesterday |
hiringMonths |
integer | 1 |
Recent monthly hiring threads to parse |
hiringThreadIds |
array | [] |
Specific hiring threads, overriding the month count |
hiringKeywords |
array | [] |
Keep matching hiring posts |
remoteOnly |
boolean | false |
Keep hiring posts that mention remote work |
maxItems |
integer | 50 |
Total records emitted; nested comments count too |
includeAuthorProfiles |
boolean | false |
Add author karma and account creation date |
startUrls |
array | [] |
Item, user, front-page, or hiring-thread links |
Empty fields are omitted from the output — there are no nulls or blank strings.
Example: search with filters
{
"mode": "search",
"searchQueries": ["rust async runtime", "tokio"],
"searchSort": "date",
"contentTypes": ["story", "comment"],
"dateRangeFrom": "2025-01-01",
"minScore": 50,
"maxItems": 200
}
Example: full comment tree
{
"mode": "item",
"itemIds": ["49922569"],
"maxComments": 300,
"maxDepth": 10,
"enableCommentHierarchy": true,
"commentSort": "newest"
}
Example: a historical front page
{
"mode": "frontPage",
"frontPageDate": "2024-01-01",
"maxItems": 500
}
Example: this month’s hiring posts
{
"mode": "whoIsHiring",
"hiringMonths": 1,
"hiringKeywords": ["python", "backend"],
"remoteOnly": true,
"maxItems": 100
}
Output per story, job, or poll
id,hnUrl,type(story,job, orpoll),titleurl,domainfor link postsscore,author,numCommentscreatedAt(ISO-8601 UTC),createdAtEpoch,ageHourstextfor Ask HN, Show HN, jobs, and pollskids— top-level comment IDsrank— feed, search, or front-page positionfrontPageDatefor historical rowspollOptions[]—id,text,votes,author,createdAt,hnUrlfetchedCommentCountwhen comments were readcomments[]— nested replies when hierarchy is enabledauthorKarma,authorCreatedAtwhen author enrichment is enableddead/deletedonly when truerecordType: "story",scrapedAt
Output per comment
id,hnUrl,type,author,textstoryId,parentId,depthcreatedAt,createdAtEpoch,ageHourskids— reply IDsstoryTitle,storyUrlwhen a search hit supplies themreplies[]in nested mode onlydead/deletedonly when truerecordType: "comment",scrapedAt
Output per user
id,profileUrlkarma,createdAt,createdAtEpoch,aboutsubmittedCount,submitted(first 50 recent IDs)recordType: "user",scrapedAt
With includeSubmissions, normal story and comment rows follow the profile.
Output per poll option
id,hnUrl,type: "pollopt",text,votes,pollIdauthor,createdAt,createdAtEpoch,ageHoursrecordType: "pollOption",scrapedAt
Output per hiring post
id,hnUrl,threadId,threadTitle,threadMonthauthor,company,role,location,remote,salarytechStack,visa,email,applyUrltext,postedAtrecordType: "jobPosting",scrapedAt
Parsed hiring fields are omitted when the post does not state them.
Usage cost
There is no paid data source, proxy, or credential in this actor. Usage is ordinary Apify compute plus the records you choose to collect. The cheapest useful run is the default prefill: 20 top stories with comments and author enrichment off. Cost grows with maxItems, maxComments, maxDepth, multiple search queries, exhaustiveSearch, and includeAuthorProfiles because each adds fetches. Small maxItems values keep runs short and inexpensive.
FAQ
Do I need an account, cookie, or API key? No. Every mode reads public Hacker News data.
Do I need a proxy? No. The actor connects directly and needs no proxy configuration.
Why is a field missing from some records? Hacker News does not store that field for every item. For example, self posts have text but no link URL, and many users have no “about” text. Missing fields are omitted instead of filled with a placeholder.
Why do comment scores never appear? Hacker News does not publish per-comment scores through its feeds, search, or HTML. Stories, polls, jobs, and poll options do have scores.
Why did a search stop at 1,000 results? Hacker News search returns at most 1,000 hits per query window. Turn on exhaustiveSearch to split the date range into smaller windows and collect deeper results.
Why is relevance order different when exhaustiveSearch is on? The deep search collects several date windows. Each window is ranked by relevance, so the final list follows window order rather than one global relevance ordering. Use searchSort: "date" for a stable chronological order.
How fresh is the data? Feeds and item lookups are live. Search and comment search can lag the live site by a short period, so brand-new comments or score changes may appear slightly later.
What is the difference between maxItems and maxComments? maxItems caps every emitted record, including nested comments. maxComments caps how many comments are read for each story before depth filtering.
Can I read a historical best, Ask HN, or Show HN list? No. Hacker News archives only the historical front page by date. Live Ask HN, Show HN, best, and job lists are available through their normal modes.
Is this affiliated with Hacker News or Y Combinator? No. This is an independent actor that reads Hacker News’ public data.
Notes
- All timestamps are UTC and ISO-8601, with a matching Unix epoch.
- Records are snapshots: scores, comment counts, and comment trees can change after a run.
- Flat comment output contains one row per comment and never repeats a reply inside another row.
- Nested comment output is one story row; every reply carries its own type and scrape timestamp.
itemreturns a comment row for a comment ID, a story-style row for a story, job, or poll, and a poll-option row for a poll-option ID.startUrlsaccepts item, user, historical front-page, and hiring-thread links alongside the mode-specific lists.- Historical front pages are deduplicated when a story appears twice on the same day.
Limitations
- No comment scores or flags. Hacker News does not expose per-comment scores, moderation flags, or edit history publicly.
- Search ceiling. Each Hacker News search window returns at most 1,000 hits.
exhaustiveSearchworks around this by date slicing, but a single second with more than 1,000 hits cannot be split further. - Historical lists. Only the front page is archived by day. Historical best, Ask HN, Show HN, and jobs pages are not available.
- Feed caps. Hacker News itself limits the live feeds: top and new stories usually expose 500 IDs, best about 200, Ask HN 20, Show HN up to about 150, and jobs about 30. The actor reports when a feed is exhausted.
- Comment-tree lag. The fast tree can trail the live thread by a short period, and deleted branches may be absent. The actor merges a comment-search fallback when live replies are missing; turning off
excludeDeadOrDeleteduses the exact slower walk. - Hiring parsing is heuristic. Company, role, location, salary, tech stack, visa, email, and apply link are extracted from free-form posts. Fields the post does not state are omitted; no value is invented.
- Very large user histories. A user can have tens of thousands of submissions.
maxItemsandsubmissionTypeskeep the run bounded. - Relevance is not deterministic. Search relevance can shift between runs as the index changes; date order is stable.
Python quickstart
Use a schema-derived input and the Python standard library to start a run. An Apify account and token are required for execution.
Source build ajANmalEbfWPogs9n. Documentation is regenerated from the default published build; private drafts are not included.