Algolia 429 Too Many Requests Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Batch your writes

   Copy steps
   1. Send records with batch operations (saveObjects) instead of one request per record
   2. Wait for task completion (waitTask) before sending the next large batch
   Did this fix it? Yes No

2. 2. Back off and retry

   Copy steps
   1. On 429, retry with exponential backoff instead of immediately
   2. Reduce parallel indexing workers
   Did this fix it? Yes No

3. 3. Check the API key rate limit

   Copy steps
   1. Go to Settings > API Keys and open the key in use
   2. Look at its max queries per IP per hour and raise or remove it, or create a dedicated key
   Did this fix it? Yes No

Symptoms

API calls fail with HTTP 429 Too Many Requests, often during bulk indexing or traffic spikes.

Why it happens

• More than 500 pending indexing requests, after which new requests are rejected (throttling starts above 100)
• Many single-record writes instead of batches
• A rate limit configured on the API key itself
• Search traffic bursts hitting a limited key

This guide also covers

• algolia 429
• algolia too many requests
• algolia rate limit

The same problem in other apps

All not loading, error messages & connection guides →

• Meilisearch Primary Key Error (Meilisearch)
• Typesense 503 Not Ready or Lagging Error (Typesense)

Other Algolia errors

• Algolia Search Returns No Results
• Algolia Search Results Irrelevant or Wrong Order
• Algolia Record Is Too Big Error
• Algolia Record Quota Exceeded or Limit Reached
• Algolia Invalid Application ID or API Key (403)
• Algolia Updates Not Showing in Search Results
• Algolia Search Slow or High Latency
• Algolia Crawler Not Indexing Records