This reference describes the general behavior of Meilisearch’s RESTful API. If you are new to Meilisearch, check out the getting started.

​
OpenAPI

You can get the Meilisearch OpenAPI specifications here.

​
Document conventions

This API documentation uses the following conventions:
  • Curly braces ({}) in API routes represent path parameters, for example, GET /indexes/{index_uid}
  • Required fields are marked by an asterisk (*)
  • Placeholder text is in uppercase characters with underscore delimiters, for example, MASTER_KEY

​
Authorization

By providing Meilisearch with a master key at launch, you protect your instance from unauthorized requests. The provided master key must be at least 16 bytes. From then on, you must include the Authorization header along with a valid API key to access protected routes (all routes except /health. 
# replace the MASTER_KEY placeholder with your master key
curl \
  -X GET 'MEILISEARCH_URL/keys' \
  -H 'Authorization: Bearer MASTER_KEY'
The /keys route can only be accessed using the master key. For security reasons, we recommend using regular API keys for all other routes.
v0.24 and below use the X-MEILI-API-KEY: apiKey authorization header:
curl \
  -X GET 'http://<your-domain-name>/version' \
  -H 'X-Meili-API-Key: API_KEY'
To learn more about keys and security, refer to our security tutorial.

​
Pagination

Meilisearch paginates all GET routes that return multiple resources, for example, GET /indexes, GET /documents, GET /keys, etc. This allows you to work with manageable chunks of data. All these routes return 20 results per page, but you can configure it using the limit query parameter. You can move between pages using offset. All paginated responses contain the following fields:
NameTypeDescription
offsetIntegerNumber of resources skipped
limitIntegerNumber of resources returned
totalIntegerTotal number of resources

​
/tasks endpoint

Since the /tasks endpoint uses a different type of pagination, the response contains different fields. You can read more about it in the tasks API reference.

​
Parameters

Parameters are options you can pass to an API endpoint to modify its response. There are three main types of parameters in Meilisearch’s API: request body parameters, path parameters, and query parameters.

​
Request body parameters

These parameters are mandatory parts of POST, PUT, and PATCH requests. They accept a wide variety of values and data types depending on the resource you’re modifying. You must add these parameters to your request’s data payload.

​
Path parameters

These are parameters you pass to the API in the endpoint’s path. They are used to identify a resource uniquely. You can have multiple path parameters, for example, /indexes/{index_uid}/documents/{document_id}. If an endpoint does not take any path parameters, this section is not present in that endpoint’s documentation.

​
Query parameters

These optional parameters are a sequence of key-value pairs and appear after the question mark (?) in the endpoint. You can list multiple query parameters by separating them with an ampersand (&). The order of query parameters does not matter. They are mostly used with GET endpoints. If an endpoint does not take any query parameters, this section is not present in that endpoint’s documentation.

​
Headers

​
Content type

Any API request with a payload (--data-binary) requires a Content-Type header. Content type headers indicate the media type of the resource, helping the client process the response body correctly. Meilisearch currently supports the following formats:
  • Content-Type: application/json for JSON
  • Content-Type: application/x-ndjson for NDJSON
  • Content-Type: text/csv for CSV
Only the add documents and update documents endpoints accept NDJSON and CSV. For all others, use Content-Type: application/json.

​
Content encoding

The Content-Encoding header indicates the media type is compressed by a given algorithm. Compression improves transfer speed and reduces bandwidth consumption by sending and receiving smaller payloads. The Accept-Encoding header, instead, indicates the compression algorithm the client understands. Meilisearch supports the following compression methods:
  • br: uses the Brotli algorithm
  • deflate: uses the zlib structure with the deflate compression algorithm
  • gzip: uses the gzip algorithm

​
Request compression

The code sample below uses the Content-Encoding: gzip header, indicating that the request body is compressed using the gzip algorithm: 
 cat ~/movies.json | gzip | curl -X POST 'MEILISEARCH_URL/indexes/movies/documents' --data-binary @- -H 'Content-Type: application/json' -H 'Content-Encoding: gzip'

​
Response compression

Meilisearch compresses a response if the request contains the Accept-Encoding header. The code sample below uses the gzip algorithm: 
curl -sH 'Accept-encoding: gzip' 'MEILISEARCH_URL/indexes/movies/search' | gzip -

​
Request body

The request body is data sent to the API. It is used with PUT, POST, and PATCH methods to create or update a resource. You must provide request bodies in JSON.

​
Response body

Meilisearch is an asynchronous API. This means that in response to most write requests, you will receive a summarized version of the task object: 
{
    "taskUid": 1,
    "indexUid": "movies",
    "status": "enqueued",
    "type": "indexUpdate",
    "enqueuedAt": "2021-08-11T09:25:53.000000Z"
}
You can use this taskUid to get more details on the status of the task. See more information about asynchronous operations.

​
Data types

The Meilisearch API supports JSON data types.