Error codes

This page is an exhaustive list of Meilisearch API errors.

A key with this uid already exists.

The requested API key could not be found.

The request is invalid, check the error message for more information.

The requested database has reached its maximum size.

A document exceeds the maximum limit of 65,535 fields.

The requested document can't be retrieved. Either it doesn't exist, or the database was left in an inconsistent state.

An error occurred during the dump creation process. The task was aborted.

The actions field of an API key cannot be modified.

The createdAt field of an API key cannot be modified.

The expiresAt field of an API key cannot be modified.

The indexes field of an API key cannot be modified.

The key field of an API key cannot be modified.

The uid field of an API key cannot be modified.

The updatedAt field of an API key cannot be modified.

The uid field of an index cannot be modified.

The updatedAt field of an index cannot be modified.

An index with this uid already exists, check out our guide on index creation.

An error occurred while trying to create an index, check out our guide on index creation.

An index with this uid was not found, check out our guide on index creation.

The requested index already has a primary key that cannot be changed.

Primary key inference failed because the received documents contain multiple fields ending with id. Use the update index endpoint to manually set a primary key.

Meilisearch experienced an internal error. Check the error message, and open an issue if necessary.

The requested resources are protected with an API key. The provided API key is invalid. Read more about it in our dedicated guide.

The actions field for the provided API key resource is invalid. It should be an array of strings representing action names.

The description field for the provided API key resource is invalid. It should either be a string or set to null.

The expiresAt field for the provided API key resource is invalid. It should either show a future date or datetime in the RFC 3339 format or be set to null.

The indexes field for the provided API key resource is invalid. It should be an array of strings representing index names.

The limit parameter is invalid. It should be an integer.

The given name is invalid. It should either be a string or set to null.

The offset parameter is invalid. It should be an integer.

The given uid is invalid. The uid must follow the uuid v4 format.

The Content-Type header is not supported by Meilisearch. Currently, Meilisearch only supports JSON, CSV, and NDJSON.

The csvDelimiter parameter is invalid. It should either be a string or a single ASCII character.

The provided document identifier does not meet the format requirements. A document identifier must be of type integer or string, composed only of alphanumeric characters (a-z A-Z 0-9), hyphens (-), and underscores (_).

The fields parameter is invalid. It should be a string.

The limit parameter is invalid. It should be an integer.

The offset parameter is invalid. It should be an integer.

The provided _geo field of one or more documents is invalid. Meilisearch expects _geo to be an object with two fields, lat and lng, each containing geographic coordinates expressed as a string or floating point number. Read more about _geo and how to troubleshoot it in our dedicated guide.

The limit parameter is invalid. It should be an integer.

The offset parameter is invalid. It should be an integer.

There is an error in the provided index format, check out our guide on index creation.

The primaryKey field is invalid. It should either be a string or set to null.

The attributesToCrop parameter is invalid. It should be an array of strings, a string, or set to null.

The attributesToHighlight parameter is invalid. It should be an array of strings, a string, or set to null.

The attributesToRetrieve parameter is invalid. It should be an array of strings, a string, or set to null.

The cropLength parameter is invalid. It should be an integer.

The cropMarker parameter is invalid. It should be a string or set to null.

This error occurs if:

• The facets parameter is invalid. It should be an array of strings, a string, or set to null
• The attribute used for faceting is not defined in the filterableAttributes list

This error occurs if:

• The syntax for the filter parameter is invalid
• The attribute used for filtering is not defined in the filterableAttributes list
• A reserved keyword like _geo, _geoDistance, or _geoPoint is used as a filter

The highlightPostTag parameter is invalid. It should be a string.

The highlightPreTag parameter is invalid. It should be a string.

The hitsPerPage parameter is invalid. It should be an integer.

The limit parameter is invalid. It should be an integer.

The matchingStrategy parameter is invalid. It should either be set to last or all.

The offset parameter is invalid. It should be an integer.

The page parameter is invalid. It should be an integer.

The q parameter is invalid. It should be a string or set to null

The showMatchesPosition parameter is invalid. It should either be a boolean or set to null.

This error occurs if:

• The syntax for the sort parameter is invalid
• The attribute used for sorting is not defined in the sortableAttributes list or the sort ranking rule is missing from the settings
• A reserved keyword like _geo, _geoDistance, _geoRadius, or _geoBoundingBox is used as a filter

The value of displayed attributes is invalid. It should be an empty array, an array of strings, or set to null.

The value of distinct attributes is invalid. It should be a string or set to null.

The value for the maxValuesPerFacet field is invalid. It should either be an integer or set to null.

The value of filterable attributes is invalid. It should be an empty array, an array of strings, or set to null.

The value for the maxTotalHits field is invalid. It should either be an integer or set to null.

This error occurs if:

• The settings payload has an invalid format
• A non-existent ranking rule is specified
• A custom ranking rule is malformed
• A reserved keyword like _geo, _geoDistance, _geoRadius, _geoBoundingBox, or _geoPoint is used as a custom ranking rule

The value of searchable attributes is invalid. It should be an empty array, an array of strings or set to null.

The value of sortable attributes is invalid. It should be an empty array, an array of strings or set to null.

The value of stop words is invalid. It should be an empty array, an array of strings or set to null.

The value of the synonyms is invalid. It should either be an object or set to null.

This error occurs if:

• The enabled field is invalid. It should either be a boolean or set to null
• The disableOnAttributes field is invalid. It should either be an array of strings or set to null
• The disableOnWords field is invalid. It should either be an array of strings or set to null
• The minWordSizeForTypos field is invalid. It should either be an integer or set to null
• The value of either oneTypo or twoTypos is invalid. It should either be an integer or set to null

The database is in an invalid state. Deleting the database and re-indexing should solve the problem.

The data.ms folder is in an invalid state. Your b file is corrupted or the data.ms folder has been replaced by a file.

The indexes used in the indexes array for a swap index request have been declared multiple times. You must declare each index only once.

This error happens if:

• The payload doesn't contain exactly two index uids for a swap operation
• The payload contains an invalid index name in the indexes array

The afterEnqueuedAt query parameter is invalid.

The afterFinishedAt query parameter is invalid.

The afterStartedAt query parameter is invalid.

The beforeEnqueuedAt query parameter is invalid.

The beforeFinishedAt query parameter is invalid.

The beforeStartedAt query parameter is invalid.

The canceledBy query parameter is invalid. It should be an integer. Multiple uids should be separated by commas (,).

The indexUids query parameter contains an invalid index uid.

The limit parameter is invalid. It must be an integer.

The requested task status is invalid. Please use one of the possible values.

The requested task type is invalid. Please use one of the possible values.

The uids query parameter is invalid.

This error generally occurs when the host system has no space left on the device or when the database doesn't have read or write access.

Primary key inference failed as the received documents do not contain any fields ending with id. Manually designate the primary key, or add some field ending with id to your documents.

The Content-Type header does not match the request body payload format or the format is invalid.

The actions field is missing from payload.

The expiresAt field is missing from payload.

The indexes field is missing from payload.

This error happens if:

• The requested resources are protected with an API key that was not provided in the request header. Check our guide on security for more information
• You are using the wrong authorization header for your version. v0.24 and below use X-MEILI-API-KEY: apiKey, whereas v0.25 and above use Authorization: Bearer apiKey

The payload does not contain a Content-Type header. Currently, Meilisearch only supports JSON, CSV, and NDJSON.

A document does not contain any value for the required primary key, and is thus invalid. Check documents in the current addition for the invalid ones.

The payload is missing the uid field.

You need to set a master key before you can access the /keys route. Read more about setting a master key at launch in our dedicated guide.

The Content-Type header was specified, but no request body was sent to the server or the request body is empty.

The index swap payload is missing the indexes object.

The cancel tasks and delete tasks endpoints require one of the available query parameters.

The host system partition has reached its maximum capacity and can no longer accept writes.

The requested resources could not be found.

The payload sent to the server was too large. Check out this guide to customize the maximum payload size accepted by Meilisearch.

The requested task does not exist. Please ensure that you are using the correct uid.

Indexing a large batch of documents, such as a JSON file over 3.5GB in size, can result in Meilisearch opening too many file descriptors. Depending on your machine, this might reach your system's default resource usage limits and trigger the too_many_open_files error. Use ulimit or a similar tool to increase resource consumption limits before running Meilisearch. For example, call ulimit -Sn 3000 in a UNIX environment to raise the number of allowed open file descriptors to 3000.

The document exists in store, but there was an error retrieving it. This probably comes from an inconsistent state in the database.