Algolia Invalid Application ID or API Key (403)

How to fix it

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

1. 1. Verify credentials

   Copy steps
   1. Open Settings > API Keys
   2. Compare the Application ID and Search-Only API Key with those in your code
   3. If a key was regenerated, update every deployment
   Did this fix it? Yes No

2. 2. Use the right key type

   Copy steps
   1. Use a search-only key in browsers and the Write/Admin key on the server only
   2. Check the key's ACL, index restrictions and referrers
   Did this fix it? Yes No

3. 3. Test with a simple call

   1. Send a search request to {APP_ID}-dsn.algolia.net with the key; a 200 means the credentials work
   Did this fix it? Yes No

Symptoms

Searches or indexing calls fail with 403 "Invalid Application-ID or API key".

Why it happens

• Wrong app ID or key copied
• The key was regenerated; old keys stop working
• Search-only key used for write operations
• Key restricted to specific indices or referrers
• Crawler apiKey missing the required ACL

This guide also covers

• algolia 403
• algolia invalid api key
• algolia invalid application id

Other Algolia errors

• Algolia Search Returns No Results
• Algolia Search Results Irrelevant or Wrong Order
• Algolia 429 Too Many Requests Error
• Algolia Record Is Too Big Error
• Algolia Record Quota Exceeded or Limit Reached
• Algolia Updates Not Showing in Search Results
• Algolia Search Slow or High Latency
• Algolia Crawler Not Indexing Records