Hacker News API

Hacker News Story comments API

List the comments on a Hacker News story by id - text, author, and timestamp as clean JSON.

$1.50/1k req, pay per request, no subscription.

What the API returnedcomments[0]
{
"id": "45389802",
"parentId": "45389217",
"author": "gwern_reader",
"text": "The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.",
"createdUtc": 1758981900,
"postId": "45389217",
"permalink": "https://news.ycombinator.com/item?id=45389802"
}
Uptime
100.00%
30d · 151 calls
Requests
152
30d · weekly, last 12 wks
Response
0.5s
median · 30d

Pricing and providers

Hacker News Story comments API pricing: one API, 2 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$15.00
$1.50/1k req, only for what you use. No monthly plan.
Your first 66 requests are free with the $0.10 starting balance.

Try it

Get Hacker News story comments in one request

Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 10 of 11 fields. See every field

{
  "found": true,
  "data": {
    "comments": [
      {
        "id": "45389802",
        "parentId": "45389217",
        "author": "gwern_reader",
        "text": "The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.",
        "createdUtc": 1758981900,
        "postId": "45389217",
        "permalink": "https://news.ycombinator.com/item?id=45389802"
      },
      {
        "id": "45389944",
        "parentId": "45389802",
        "author": "tuple_of_one",
        "text": "Bazel does crate level caching too if you use rules_rust, curious why they rolled their own instead.",
        "createdUtc": 1758983160,
        "postId": "45389217",
        "permalink": "https://news.ycombinator.com/item?id=45389944"
      },
      {
        "id": "45390110",
        "parentId": "45389217",
        "author": "kvasir_dev",
        "text": "Author here. We looked at Bazel first, the migration cost for our existing Go and TypeScript services was the blocker, not the caching model.",
        "createdUtc": 1758984720,
        "postId": "45389217",
        "permalink": "https://news.ycombinator.com/item?id=45390110"
      }
    ]
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • idstring

    45389217

    Hacker News story id, e.g. "47340079".

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

each commentdata.comments[]

Comments on the story. Populated whenever the provider has data for the entity.

  • authorstring

    gwern_reader

    Commenting user's username. Populated whenever the provider has data for the entity.

  • createdUtcnumber

    1758981900

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.

  • idstring

    45389802

    Hacker News comment id. Populated whenever the provider has data for the entity.

  • parentIdstring

    45389217

    Id of the parent item (story or comment) this reply belongs to.

  • permalinkstring

    https://news.ycombinator.com/item?id=45389802

    Permalink to the item on news.ycombinator.com.

  • postIdstring

    45389217

    Hacker News item ID of the story the comment belongs to.

  • textstring

    The interesting bit here is not Rust itself, it is that they went from a 40 minute cold build to under 3 minutes by caching at the crate graph level instead of the file level. That is a build system design decision, not a language one.

    Comment body text.

top level
  • foundboolean

    true

    True when the story id resolved and comments were returned.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the Hacker News Story comments API

The AnyAPI Hacker News Story comments API returns Hacker News story comments data as normalized JSON from one POST call to /v1/run/hackernews.story_comments. List the comments on a Hacker News story by id - text, author, and timestamp as clean JSON. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Hacker News story comments calls through AnyAPI succeeded, with a median response time of 0.5 seconds across 151 measured calls.

It costs from $1.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

List the comments on a Hacker News story by id - text, author, and timestamp as clean JSON. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Hacker News story comments calls through AnyAPI succeeded, with a median response time of 0.5 seconds across 151 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 66 Hacker News Story comments calls at $0.0015 each.

AnyAPI asks the next of its 2 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/hackernews.story_comments with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.