Question
Why does the Algolia .NET client return 'Not enough rights to add an object' even when I believe I have write permissions?
Lax Lane
0 reputation · 20 Dec 2024, 08:58 UTC
147.5K views1
Loading…
0 reputation · 20 Dec 2024, 08:58 UTC
When attempting to push records to an Algolia index with the .NET client, the operation sometimes fails with a "Not enough rights to add an object" message despite the expectation that the supplied API key grants write access. The goal is to determine whether the failure stems from an ACL mismatch, key selection, or client configuration, while working within an existing .NET project that already references the Algolia.Search package.
How can I verify that the API key actually being used by the client possesses the addObject ACL? What diagnostic details does the Algolia API return to differentiate missing write rights from other authentication problems? In scenarios where multiple keys are configured, what steps can I take to isolate and confirm the exact key employed by the client during the AddObjects call?
26525 reputation · 20 Dec 2024, 10:23 UTC
Assumptions: You have an Algolia account, an Admin API key (or a key with write permissions), a .NET project referencing the Algolia.Search NuGet package, and you are trying to push records with index.AddObjects(batch).
algoliavar client = new AlgoliaSearchClient("YourApplicationID", "YourAPIKey");var index = client.InitIndex("your_index_name");addObject ACL. In the Algolia dashboard go to API Keys, edit the key, and ensure the addObject checkbox is ticked (or use the Admin key which has all ACLs).List<MyRecord> from a JSON file.var res = await index.AddObjectsAsync(batch); and inspect res.IsSuccess or the errors list.addObject (or the Admin key), repeat step 5, and verify that res.IsSuccess is true.var hits = await index.SearchAsync<MyRecord>(new Query("")); and check that hits.NbHits matches the number of objects you added.await index.ClearObjectsAsync(); then re‑index with the correct key.Use comments to ask for clarification. Post a solution as an answer.
26,525 reputation · 20 Dec 2024, 15:34 UTC
While checking the general addObject ACL is the first step, it is important to verify if the API key has index-specific restrictions. In Algolia, a key can possess the correct ACL globally but be restricted to a specific set of indices.
If you are using a restricted key, ensure the target index name matches exactly what is defined in the key's restricted indices list. If the index is not listed, the API will return a 403 Forbidden error with the "Not enough rights" message, even if the addObject permission is enabled.
addObject and then check the Restricted Indices field to ensure your specific index is permitted.