# Hacker News Story Comments (`hackernews.story_comments`)

Every comment of a Hacker News story, flattened depth-first with parent ids, authors, timestamps and depth.

Docs: https://primaryapi.com/docs/api-reference/hackernews/story_comments

- Endpoint: `POST https://api.primaryapi.com/v1/run/hackernews.story_comments`
- Category: Social · Platform: `hackernews` · Kind: list · Status: live
- Price: 1 credit per call. Every call costs the same, including calls that were retried automatically.
- Billing unit: per successful call
- Reliability: routed to a healthy upstream and retried automatically when an attempt fails; live 30-day status: `GET https://api.primaryapi.com/v1/status/apis?sku=hackernews.story_comments`
- Execution: synchronous (answers 202 only if it outlives the wait window)

## Input

| Field | Type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
| `id` | string | yes |  | pattern: ^(?:\d{1,12}\|https?:\/\/news\.ycombinator\.com\/item\?id=\d{1,12}(?:&\S*)?)$ | Hacker News story id, e.g. "8863" (an item URL such as https://news.ycombinator.com/item?id=8863 also works). |
| `limit` | integer | no | 500 | 1–1000 | Maximum number of results to return (1-1000, default 500). |
| `cursor` | string | no |  |  | Opaque pagination cursor: pass the previous response's nextCursor. |

Unknown fields are rejected with `400 invalid_input`. The routing controls `preferLatencyUnderMs` and `maxCredits` may be sent in the same JSON body.

## Output

When `output.found` is `true`, `output.data` has this shape:

| Field | Type | Description |
|---|---|---|
| `comments` | object[] |  |
| `comments[].id` | string |  |
| `comments[].parentId` | string \| null | Id of the item this comment replies to (the story id for top-level comments) |
| `comments[].postId` | string | Story id |
| `comments[].author` | string \| null |  |
| `comments[].text` | string \| null | Comment HTML as published on HN (raw, sanitise before display) |
| `comments[].createdUtc` | integer \| null | Creation time, UTC epoch seconds |
| `comments[].depth` | integer | Nesting depth, 0 = top-level comment |
| `comments[].permalink` | string |  |
| `nextCursor` | string \| null | Pass as `cursor` for the next comments; null when the thread is complete |

When the thing you asked about does not exist (or a search matches nothing) the call still succeeds: `output.found` is `false`, `output.data` is `null` and `output.reason` says why (`not_found`, `private`, `no_results`, …). Misses are free unless the notes below say misses are billed.

Pagination: pass the previous response’s `nextCursor` as `cursor` to get the next page; `nextCursor: null` means there are no more results.

## Example request

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/run/hackernews.story_comments" \
  -H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":"8863"}'
```

## Example response

_Values are placeholders that follow the output schema; `credits` is what this call would cost at the usual price._

```json
{
  "output": {
    "found": true,
    "data": {
      "comments": [
        {
          "id": "8863",
          "parentId": "string",
          "postId": "string",
          "author": "string",
          "text": "string",
          "createdUtc": 0,
          "depth": 0,
          "permalink": "string"
        }
      ],
      "nextCursor": null
    }
  },
  "provider": "PrimaryAPI",
  "credits": 1,
  "items": 1,
  "requestId": "req_01JBXK6Y2N9V8T4R3Q2P1M0A7Z",
  "nextCursor": null
}
```

## Pricing and reliability

- Usual price: 1 credit per call
- Price ceiling: the usual price, even when a call is retried. A quote’s `maxCredits` is the most a given call can cost; the `maxCredits` routing control caps it per call
- Live 30-day status, success rate, uptime and latency: `GET https://api.primaryapi.com/v1/status/apis?sku=hackernews.story_comments`

## Errors to handle

`invalid_input`, `unauthorized`, `insufficient_balance`, `key_limit_reached`, `trial_cap_reached`, `forbidden`, `not_found`, `idempotency_conflict`, `rate_limited`, `all_sources_failed`, `service_unavailable`, `timeout`. See https://primaryapi.com/docs/errors.

## Notes

Order: depth-first, siblings oldest first (ascending id); deleted comments are skipped but their replies kept; dead (flagged) comments are skipped with their replies, as on news.ycombinator.com. Fallback; deeper pages need the primary). Comment text is raw HN HTML.

## Legal

Comment authors are personal data under GDPR/CCPA (pseudonymous usernames): use for lawful purposes only and honour deletions. Deleted comments are never returned.

