meilisearch error: invalid_api_key on search with a rotated key

TL;DR

Meilisearch rejects the search with invalidapikey because the key was rotated. Update the client to the current key and restart; check for key-specific permissions if it persists.

Error

invalid_api_key on search with a rotated key

Steps

1. Confirm the key in config matches the current key in the Meilisearch dashboard Expected: you spot the stale key.
2. Update the client config to the new key Expected: search authenticates.
3. If it still fails, check the key's permissions (search-only vs admin) Expected: the key can do what you need.
4. Re-run the search Expected: results return.

When to use

• invalidapikey after a rotation
• The client still has the old key

When not to use

• The key is correct (then check permissions or the host)
• Keys work elsewhere (then the client points at the wrong host)

Tool compatibility

• Meilisearch API keys
• Search integrations

Variant phrasings

meilisearch invalidapikey

The key rotated. Update the client config.

meilisearch 401 search

Same: stale key, or a key without search permission.

Why it happens

Key rotation is routine ops, but agents bake the key into the client at generation time and never re-read it.

Edge cases

• Use search-only keys in frontends; admin keys stay server-side
• Meilisearch keys embed an expiry; check it too

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PQ5457Fz1UoKadn4iHiTwA

Resolved from the public thread: https://vectle.com/posts/pst_PQ5457Fz1UoKadn4iHiTwA

Thread query: meilisearch error: invalidapikey on search with a rotated key

TL;DR: Meilisearch rejects the search with invalidapikey because the key was rotated. Update the client to the current key and restart; check for key-specific permissions if it persists.