Social Fetch
Get API key
Hacker News hub

Hacker News User Submissions API

Page a user's stories, polls, and jobs newest first — for author history without scraping the submissions HTML.

GET /v1/hackernews/users/{username}/submissions

1 credit per successful request.

Try in playgroundFull API docs

About this endpoint

Founder research and competitive monitoring often need everything an HN account has submitted: Show HN launches, essays, polls, and job posts. Hand-paging the submissions HTML does not scale, and rebuilding that list from search alone misses items that never matched your keywords.

`GET /v1/hackernews/users/{username}/submissions` lists stories, polls, and jobs for a case-sensitive username, newest first. Optional zero-based `page` and `pageSize` (1–50, default 20) control the window (up to 1,000 accessible hits). On `found`, `data.user` echoes the profile URL, `data.items` holds hydrated rows, and `data.page` reports hasMore and nextPage. `not_found` returns null user and empty items.

Credit pricing for this operation comes from the API registry and appears on this page, and `meta.creditsCharged` is the billing source of truth. For comments or public favorites, use the sibling routes under the same username.

Hacker News User Submissions API FAQ

How do I list a Hacker News user's submissions?

Call GET /v1/hackernews/users/{username}/submissions with your Social Fetch API key in the x-api-key header. Pass the case-sensitive username. Optionally set page and pageSize. Read data.lookupStatus, then data.items.

How many credits does listing user submissions cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

What item types appear in submissions?

Stories, polls, and jobs — newest first. Comments are not included here; use GET /v1/hackernews/users/{username}/comments for the comment stream.

How does pagination work on user submissions?

Use zero-based page and pageSize. When data.page.hasMore is true, request nextPage with the same username and pageSize. Accessible history is capped (see page metadata / max hits in the API docs).

What does lookupStatus mean?

found means the username resolved and items may be returned. not_found means the user does not exist. HTTP 200 still means the request finished; always branch before writing.

Submissions vs search by author?

This route is the user's submission history. Search with an author filter is full-text discovery across the index and can include comments depending on type. Prefer submissions for complete author story/job/poll history.

Can I use this for author history jobs?

Yes. Teams page submissions after a profile lookup, store item ids, and hydrate details with stories or items routes when needed. Log meta.requestId per page.

Other Hacker News endpoints