What causes "Meilisearch Primary Key Error"?

No attribute ending in id (case-insensitive) in the first document Several attributes end in id Trying to change the primary key while documents exist

How do I fix "Meilisearch Primary Key Error"?

1. Set the primary key explicitly: Add documents with ?primaryKey=your_field, for example POST /indexes/movies/documents?primaryKey=movie_code Or create the index first with POST /indexes and a primaryKey 2. Change an existing primary key: You can't change it while documents exist Delete all documents, update the index primary key, then add the documents again

Meilisearch Primary Key Error

Workaround available Self-hosted, Meilisearch Cloud Updated November 15, 2026Based on 2 user reportsHow we research

Quick answer

Meilisearch infers the primary key from the first attribute ending in id. If there is none or several, the task fails: set the primary key yourself when adding documents.

Most likely fix: Set the primary key explicitly

How to fix it

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

1. Set the primary key explicitly
1. Add documents with ?primaryKey=your_field, for example POST /indexes/movies/documents?primaryKey=movie_code
2. Or create the index first with POST /indexes and a primaryKey
Did this fix it?
2. Change an existing primary key
1. You can't change it while documents exist
2. Delete all documents, update the index primary key, then add the documents again
Did this fix it?