Algolia search cache invalidation limits for immediate index updates

Direct answer

No. Algolia does not provide a supported, documented API parameter or HTTP header to bypass the CDN edge cache for an individual search request. The cache parameter in the JavaScript client only disables client-side (browser/in-memory) caching. For near-real-time inventory or pricing, the reliable pattern is to disable client caching, accept eventual consistency at the edge, and validate critical values through a separate authoritative read.

Confirmed behavior vs. likely explanation

Confirmed: The cache flag controls the JavaScript client's local response retention. Algolia manages its own HTTP caching headers at the CDN layer; user-supplied Cache-Control request headers are not a documented bypass mechanism, and no plan tier is documented to honor them for search queries.

Likely explanation: Staleness comes from two independent layers: replica propagation delay after an index write, and edge CDN caching of a previously valid response. Because the CDN fronts the search cluster, a cache hit can return data that was accurate when cached but is now behind the latest replica state. Algolia does not expose a per-request toggle for this infrastructure layer.

Steps for this case

1. Disable the client cache. In the JavaScript client, set cache: false during initialization (or per request, depending on your client version). This removes the browser/in-memory layer.
2. Do not rely on custom headers. Sending Cache-Control: no-cache from your application is not a documented Algolia search bypass and may be ignored at the edge.
3. Validate critical data separately. Treat search as discovery. Before rendering a price or stock level, fetch the authoritative record via getObject or your own backend. This decouples correctness from search latency.
4. Verify the staleness source. Update a record, then immediately repeat the identical search from different geographic regions with local caching disabled. If results differ by region, replica propagation is the bottleneck. If they match but lag behind your write, the edge cache is serving an older snapshot.

Assumptions and verification

This guidance assumes a standard Algolia Search plan with default CDN-backed infrastructure and a recent JavaScript client. Algolia does not document plan-specific edge-cache bypass headers. Because infrastructure behavior can change, verify against the current reference for your client library version. If you observe staleness only in server-side SDK responses and not in the browser, the cache flag is irrelevant and the delay is purely edge or replica propagation.