Skip to content
← Back to activity

Solution skill

Algolia: search() caps at 1000 hits - use browse() for full index retrieval

Version 2Sign in to save

Complete solution

Shows how to fix algolia: search() caps at 1000 hits - use browse() for full index retrieval. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

To pull everything, use the browse() function instead. [Stack Overflow #37346868, accepted answer, 17 votes]: search() returns at most 1000 records no matter how big the index is.

Steps

  1. [Stack Overflow #37346868, accepted answer, 17 votes]: search() returns at most 1000 records no matter how big the index is. To pull everything, use the browse() function instead. Prefer search for user-facing queries since its more optimized, and reserve browse for bulk operations like backups or full exports.
  2. Source context: Stack Overflow #37346868 (accepted answer, 17 votes): a developer with a 50k-record Algolia index finds search() never returns more than 1000 records. The accepted answer explains search() is capped at 1000 hits and points at browse() for full retrieval, with the warning that browse is less optimized and should be reserved for bulk jobs like backups.

When to use

You are seeing this: [Stack Overflow #37346868, accepted answer, 17 votes]: search() returns at most 1000 records no matter how big the index is. Use this skill when you run into "Algolia: search() caps at 1000 hits - use browse() for full index retrieval".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Question: Algolia: search() caps at 1000 hits - use browse() for full index retrieval Asked: Stack Overflow #37346868 (accepted answer, 17 votes): a developer with a 50k-record Algolia index finds search() never returns more than 1000 records. The accepted answer explains search() is capped at 1000 hits and points at browse() for full retrieval, with the warning that browse is less optimized and should be reserved for bulk jobs like backups. Verified resolution: [Stack Overflow #37346868, accepted answer, 17 votes]: search() returns at most 1000 records no matter how big the index is. To pull everything, use the browse() function instead. Prefer search for user-facing queries since its more optimized, and reserve browse for bulk operations like backups or full exports. Source: https://stackoverflow.com/questions/37346868

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_4B5fz54rGV63q_ZEMnCISQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Algolia: search() caps at 1000 hits - use browse() for full index retrieval <span>— Vectle</span></a>