Tutorial · Python
How to scrape Hacker News profiles with Python (2026)
A Python walkthrough for GET /v1/hackernews/users/{username}. Copy the snippet, run it, then read the JSON.
GET /v1/hackernews/users/{username} · 1 credit per successful request.
In this tutorial
You'll pull a public Hacker News profile and see the fields you get back.
Example job: refresh a creator roster from Hacker News handles you already have.
Step 1
Get ready
You need a Social Fetch API key and a working Python 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.
Python setup. Python 3 with requests installed (pip install requests). Export SOCIALFETCH_API_KEY.
When you're done, SOCIALFETCH_API_KEY is set in your shell.
Step 2
Make the request
Copy the Python snippet, keep SOCIALFETCH_API_KEY in the environment, and send GET /v1/hackernews/users/{username} with the x-api-key header. Example path: /v1/hackernews/users/pg. The sample uses public values for profiles.
You should see HTTP 200, then response.json() with data and meta. Call raise_for_status() before parsing.
Step 3
Read the response
A JSON body with data (the profiles) 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
this route is the user card only — submissions, comments, and favorites are sibling endpoints. not_found means no public user matched; do not invent a stub row.
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/users/{username} 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 users endpoint return?
A JSON envelope with data (the profiles) and meta (creditsCharged, requestId). Shape details and field docs live on the endpoint page and in the OpenAPI docs.
Does the Hacker News user endpoint return submissions?
No. This route returns the user card only. For submissions use GET /v1/hackernews/users/{username}/submissions; for comments and favorites use the matching sibling routes.
What does not_found mean on a Hacker News user?
not_found means no public user matched that username. HTTP 200 still means the request finished. Always branch on lookupStatus before writing rows.
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 Python-specific tips for this request?
Yes. Call response.raise_for_status() before response.json(), set a timeout on requests.get, and keep response.json()["meta"]["requestId"] when a row looks wrong.
Related