Hacker News story API

Endpoint

GET/v1/hackernews/storylive · proven1 credit

Parameters

Query parameters

Name	Required	Description	Example
`id`	yes	Numeric Hacker News item id	`8863`
`dry_run`	no	Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution.	`1`

Examples

Make the request

curl

curl "https://www.monocrawl.com/v1/hackernews/story?id=8863" \
  -H "x-api-key: mn_your_key_here"

TypeScript

typescript

const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
  "https://www.monocrawl.com/v1/hackernews/story?id=8863",
  { headers: { "x-api-key": key } },
);
const body = await res.json();

if (!body.success) {
  // one error shape for every endpoint — see /docs/errors
  throw new Error(`${body.error.type}: ${body.error.message}`);
}

console.log(body.data, "credits left:", body.credits_remaining);

Python

python

import os
import requests

res = requests.get(
    "https://www.monocrawl.com/v1/hackernews/story?id=8863",
    headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
    timeout=60,
)
body = res.json()

if not body["success"]:
    # one error shape for every endpoint — see /docs/errors
    raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")

print(body["data"], "credits left:", body["credits_remaining"])

Response

Response fields and example

This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.

200 · application/json

{
  "success": true,
  "platform": "hackernews",
  "endpoint": "/v1/hackernews/story",
  "data": {
    "id": "12345",
    "title": "Example story",
    "hn_url": "https://news.ycombinator.com/item?id=12345",
    "points": 42
  },
  "credits_used": 1,
  "credits_remaining": 99,
  "request_id": "req_…",
  "cached": false
}

The example uses fictional values and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.

Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.

Field inside data	Type	Meaning
`id`	`string \| null`	Source identifier. Preserve its exact string value; do not convert large IDs to numbers.
`type`	`string \| null`	Source item kind.
`title`	`string \| null`	Story title.
`url`	`string \| null`	External story destination when supplied.
`hn_url`	`string \| null`	Hacker News discussion URL.
`author`	`string \| null`	Hacker News username.
`points`	`number \| null`	Points reported by the source; null or absent is unknown, not zero.
`comments_count`	`number \| null`	Comments in the selected source response reported by the source; null or absent is unknown, not zero.
`text`	`string \| null`	Source text, which can contain HTML.
`story_id`	`string \| null`	Source identifier. Preserve its exact string value; do not convert large IDs to numbers.
`parent_id`	`string \| null`	Source identifier. Preserve its exact string value; do not convert large IDs to numbers.
`created_at`	`string \| null`	Source publication time, normalized to an ISO date-time when available.
`_warnings`	`array`	Collection limitations or component warnings. Read before interpreting coverage.

Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference

Hacker News story

Query parameters

Make the request

Response fields and example

More Hacker News reference

First call in under a minute