Tutorial · Node.js
How to scrape Hacker News stories with Node.js (2026)
A Node.js walkthrough for GET /v1/hackernews/stories/{id}. Copy the snippet, run it, then read the JSON.
GET /v1/hackernews/stories/{id} · 1 credit per successful request.
In this tutorial
You'll pull a public Hacker News story and see the fields you get back.
Example job: hydrate a Hacker News story by id for digests or alerts.
Step 1
Get ready
You need a Social Fetch API key and a working Node.js environment. New accounts include 100 free credits.
API key. Create a Social Fetch account and copy an API key. New accounts include 100 free credits.
Node.js setup. Node 18+ (native fetch). Export SOCIALFETCH_API_KEY.
When you're done, SOCIALFETCH_API_KEY is set in your shell.
Step 2
Make the request
Copy the Node.js snippet, keep SOCIALFETCH_API_KEY in the environment, and send GET /v1/hackernews/stories/{id} with the x-api-key header. Example path: /v1/hackernews/stories/8863. The sample uses public values for stories.
You should see HTTP 200 and a JSON body. Native fetch does not throw on 4xx/5xx, so check response.ok before parsing.
Step 3
Read the response
A JSON body with data (the stories) and meta (creditsCharged, requestId). The sample below is illustrative; field-level docs live on the endpoint page. Credits charge on completed lookups, not transport failures.
Branch on data.lookupStatus when present, then keep meta.requestId if a row looks wrong.
Watch out
not_story means the id resolved but is not a story (for example a comment or job). Use GET /v1/hackernews/items/{id} when you need a polymorphic item. Comment trees are a separate paginated operation.
Step 4
You finished
Same path and credits in playground, docs, and production. Pick a next action below.
FAQ
Common questions
Do I need an official Hacker News developer account?
No. Social Fetch authenticates with your Social Fetch API key. You call GET /v1/hackernews/stories/{id} and we handle upstream access. You still need to follow each platform's terms for how you use public data.
What does the hacker news stories endpoint return?
A JSON envelope with data (the stories) and meta (creditsCharged, requestId). Shape details and field docs live on the endpoint page and in the OpenAPI docs.
Story get vs item get on Hacker News?
GET /v1/hackernews/stories/{id} expects a story and returns typed not_story when the id is another type. GET /v1/hackernews/items/{id} returns the polymorphic item for any HN id.
Does story get include the full comment tree?
No. Use GET /v1/hackernews/stories/{id}/comments for cursor-paginated comments. This route stops at the story card.
How much does a successful request cost?
1 credit per successful request.
Is this okay for production?
Yes. Same production API as the rest of Social Fetch: typed errors, requestId on every response, and credit charges only on completed lookups (not infrastructure failures). New accounts get 100 free credits.
Any Node.js-specific tips for this request?
Yes. Native fetch does not throw on 4xx/5xx — check response.ok (or status) before parsing JSON. Read meta.requestId from the body when you need support on a bad row.
Related