Hacker News search
Full-text search of Hacker News stories and comments: title, URL, text, author, points, comment count, time, parent and story ids and a link to the discussion. Filter by tags (story, comment, poll, job, ask_hn, show_hn, front_page), author, one story's thread, a date range, minimum points or comments; sort by relevance or by date (newest first). next_page is null on the last page.
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
query | string | Words to search for in titles, URLs and comment text. Leave empty with filters to list by date. Example: rust |
tags | string | Comma-separated filters, all must match: story, comment, poll, job, ask_hn, show_hn, front_page. Example: story |
author | string | Only items by this username. |
story_id | string | Only comments and the story in this story's thread. |
sort | string | relevance (default) or date (newest first). Example: date |
start | string | Posted on/after (YYYY-MM-DD). |
end | string | Posted on/before (YYYY-MM-DD). |
min_points | integer | Only items with at least this many points. |
min_comments | integer | Only items with at least this many comments. |
page | integer | Page number (default 1). |
limit | integer | Results per page (default 20, max 100). |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/hackernews/v1/search?query=rust" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/hackernews/v1/search",
params={"query": "rust"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/hackernews/v1/search");
url.searchParams.set("query", "rust");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).