Skip to main content
Send indexing operations in batches to reduce network calls and speed up indexing. Each batch groups multiple in a single API request. For example, sending one million records individually requires one million indexing requests. Sending them in batches of 1,000 reduces this to 1,000 requests. Algolia accepts up to , but for better indexing performance, keep each batch below 10 MB. The number of records per batch depends on their average size. Two things to keep in mind:
  • Batching records doesn’t reduce your operations count. Algolia counts indexing operations per record, not per method call, so from a pricing perspective, batching records is the same as indexing records individually.
  • Be careful when approaching your plan’s record limit. If you’re close to the record limit, batch operations may fail. The error message “You have exceeded your Record quota” means the engine doesn’t know if the batch operation updates or adds records. If this happens, upgrade to a plan with a higher record limit or reduce your batch size.

Manage records with the API

To run the code examples on this page, install the latest API client. When using the saveObjects method, the API clients automatically chunk your records into batches of 1,000. With this approach, you would make 1,000 indexing requests instead of a million. Depending on your records’ sizes and your network speed, you could create bigger or smaller chunks.
If you use an Algolia-managed transformation to process records, use saveObjectsWithTransformation instead of saveObjects. Like saveObjects, it uploads records in batches, but sends each batch through the configured Push to Algolia connector. For more control over the batch size or indexing action, call chunkedPush on the Ingestion client directly. For more information, see:

Manage records in the dashboard

Last modified on October 21, 2026