iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A search response can report 29,152 matching Hacker News stories while returning only 1,000 rows. Those figures describe different things: the match count is not a promise that every match can be retrieved through ordinary pagination. In a query run on September 20, 2026, the HN search endpoint returned that exact count for a particular date-bounded story search, but supplied 1,000 hits and reported one page. Treat 29,152 as a dated example, not a current HN total.
What the 29,152 figure means
The reported query used Hacker News Search API’s /api/v1/search_by_date endpoint with tags=story, a lower bound of created_at_i>1756070000, and hitsPerPage=1000. In the September 20, 2026 run, the response reported nbHits=29152, returned 1,000 hits, and showed nbPages=1 (Listwright’s dated query report). The count represents matching records reported by the index; it does not mean that all 29,152 were delivered in that response.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
The Phantom Tollbooth | $7.64 | Buy on Amazon |
| 2 |
|
Measures of Success Flute Book 1 | $8.95 | Buy on Amazon |
| 3 |
|
1,000 Books to Read Before You Die: A Life-Changing List | $19.37 | Buy on Amazon |
| 4 |
|
Measures of Success Percussion Book 2 | $16.95 | Buy on Amazon |
| 5 |
|
Developmental Exercises for Hacker Handbooks | $18.99 | Buy on Amazon |
In this example, the response exposed about 3.4% of the reported matches (1,000 divided by 29,152). That calculation describes this response only, not a general HN API retrieval rate.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Why the count and page total can disagree
Algolia distinguishes the number of matching records from the number of hits accessible through pagination. Its support documentation explains that paginationLimitedTo sets the maximum number of hits available through pagination. With the default limit of 1,000, a response can report more matching records than the pagination interface makes accessible. Algolia illustrates this with 1,500 matches, 10 hits per page, and 100 pages: the displayed pages still reach only 1,000 hits (Algolia Support, 2025).
#1 Best Overall
There are two separate caps to keep in mind. hitsPerPage controls how many hits a single page can contain, and Algolia’s documentation says it is capped at 1,000. The separate paginationLimitedTo setting controls the maximum number of hits accessible across pagination (Algolia Support, 2026). Asking for a larger page size therefore does not necessarily make more of the total result set accessible.
How to tell whether you have the complete result set
Check the returned rows and pagination metadata, not just nbHits. If a response reports a large total but returns fewer records than that total, inspect the effective hitsPerPage, nbPages, and any pagination ceiling that applies to the index. In the reported HN query, a request for 2,000 rows was answered with hitsPerPage: 1000 and 1,000 returned rows (Listwright’s September 20, 2026 query report).
Rank #2
- Use the response’s effective values rather than assuming the server accepted the requested page size.
- Compare the number of unique record IDs you actually collected with the reported count.
- Do not treat a one-page response as proof that all reported matches were retrieved when the returned page is capped.
This matters if you calculate totals, averages, or rankings: analyzing only the accessible prefix may produce results that do not represent all matches.
Ways to retrieve more records
If you control the Algolia index
An index owner can raise paginationLimitedTo, which Algolia documents as configurable up to 20,000. A higher setting may slow searches, and Algolia warns that result ordering beyond the 1,000th hit is not guaranteed when the limit exceeds 1,000 (Algolia Support, 2025). This is an option for an index operator, not a setting a consumer can necessarily change on a public endpoint.
Rank #3
- Book - 1, 000 books to read before you die: a life-changing list (1000 before you die)
- Language: english
- Binding: hardcover
If you are querying the public HN endpoint
A practical workaround reported for the HN endpoint is to split a broad time range into smaller, bounded slices so each request stays within the accessible-result ceiling. The reported technique moves the next time bound to the oldest returned record, collects IDs using objectID to remove repeats at slice boundaries, and stops when a slice adds no new IDs. The endpoint’s current configuration and this technique’s behavior are not independently guaranteed by Algolia documentation, so verify the output for the query you need (Listwright’s dated query report).
- Choose a bounded time interval and query it with the same story filters.
- Record the returned
objectIDvalues and deduplicate them across requests. - Move the next interval boundary to the oldest returned record, taking care to handle repeated timestamps and boundary overlap.
- Continue until the interval is exhausted or a slice adds no new IDs, then reconcile the collected IDs and bounds against the first slice’s reported total.
Keep the first slice’s nbHits as the total for the original query. A final narrow or empty slice may report zero; that does not reset the total for the full interval. Do not claim complete capture unless the time bounds and collected unique IDs support it.
When pagination is the wrong retrieval method
For an index owner who needs all records rather than search results, Algolia documents a browse method that retrieves index records without pagination. Algolia explicitly says browse should not be used for search (Algolia’s browse documentation). It is not a method shown as available to a consumer of the public HN endpoint.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteThe key distinction is the task: pagination is for navigating search results, while bulk retrieval calls for an appropriate record-export or browsing mechanism where the index owner permits one. Neither a large nbHits value nor a seemingly plausible sample establishes that a paginated dataset is complete.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
