Get a Hacker News story’s comments
Retrieve a nested Hacker News comment tree with comment fields and children. Bound the walk with depth and limit to read only the levels you need. Deleted comments retain null author and text values, and coverage describes the returned tree.
/v1/hackernews/story/commentsx-api-keyHeaders
Get your API keyYour ScrapeAtlas customer key. Create one on /account/ and set SCRAPEATLAS_API_KEY.
Required numeric Hacker News item ID; a comment ID returns that comment’s subtree.
8863Reply levels to return, 1–128; top-level comments are depth 1. Defaults to the whole tree. Truncated levels report depth_limit partial coverage.
2Maximum comment nodes to return, 1–5,000; defaults to 5,000. A truncated tree reports comment_limit partial coverage.
Request correlation identifier.
HTTP attempts, decoded bytes and duration for the operation, including the single shared retry.
Always included.
≥ 0
Always included.
≥ 0
Always included.
≥ 0
True when usable data is returned; inspect status and coverage for omissions.
success, partial, failed, or challenged. HTTP 200 can be partial.
one of: success, partial
Public Hacker News search, item or user URL for the request.
absolute HTTPS URL
UTC retrieval time.
Complete means this bounded page or tree was returned without known omissions. It does not imply all matching items were enumerated.
Always included.
Always included.
Always included.
Required numeric Hacker News item ID; a comment ID returns that comment’s subtree.
≥ 1
Source type of the requested item.
min 1 chars
Number of comment nodes returned across all levels.
≥ 0
Deepest reply level present in the returned tree.
≥ 0
Nested source comment nodes: id, author, text, created_at, created_at_i, parent_id, story_id, points, type, childCount (replies the source holds, including any not returned) and children, recursively, in source order.
up to 5000 items
No fields match.
HTTP 200 returns the success variant. Check status: partial means usable data with warnings, and failed or challenged requests carry a failure object described in Errors & responses.
| HTTP | failure.code | Meaning |
|---|---|---|
| 200 | partial | Usable data with comment_limit, depth_limit, children_limit or counts_unavailable warnings. |
| 400 | invalid_request | Missing, duplicate, malformed or unsupported parameters, including a search that selects nothing. |
| 401 | unauthorized | Missing or invalid worker API key. |
| 404 | not_found | The source reports a missing item or user. |
| 429 | upstream_rate_limited | Source throttling; no automatic retry. |
| 502 | upstream_challenged | Source rejected the unauthenticated request. |
| 502 | unsupported_page | Malformed, mismatched or non-JSON source data. |
| 502 | response_too_large payload_too_complex | Response exceeded byte or parsing limits. |
| 502 | unsafe_redirect request_limit upstream_error | Bounded source retrieval could not complete. |
| 503 | busy | All worker slots are occupied. |
| 504 | timeout | Total request deadline expired. |