Meilisearch Invalid API Key / Missing Authorization Header

How to fix it

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

1. 1. Send the key correctly

   Copy steps
   1. Use the header Authorization: Bearer YOUR_KEY
   2. Use the Default Search key for the frontend, Default Admin key for adding documents and settings
   Did this fix it? Yes No

2. 2. Set or recover keys

   Copy steps
   1. Start with --master-key or MEILI_MASTER_KEY, at least 16 bytes of UTF-8
   2. List keys with GET /keys using the master key
   3. On Meilisearch Cloud the master key is generated per project in the dashboard
   Did this fix it? Yes No

3. 3. Never expose admin or master keys

   Copy steps
   1. Use the master key only to manage API keys
   2. Create a scoped key with limited actions and indexes for public use
   Did this fix it? Yes No

Symptoms

Requests return missing_authorization_header or invalid_api_key; /keys returns missing_master_key.

Why it happens

• No Authorization: Bearer header sent
• Wrong or deleted key, or a key made on another instance
• No master key set, so /keys is unavailable
• Expired key (expiresAt in the past)

This guide also covers

• meilisearch invalid api key
• meilisearch missing authorization header
• meilisearch master key

The same problem in other apps

All missing or lost data guides →

• Typesense Search Returning No Results or Missing Typos (Typesense)
• Algolia Updates Not Showing in Search Results (Algolia)

Other Meilisearch errors

• Meilisearch Tasks Stuck on Enqueued
• Meilisearch Indexing Slow
• Meilisearch Documents Not Showing Up
• Meilisearch Primary Key Error
• Meilisearch Filter Not Working (Attribute Not Filterable)
• Meilisearch Database Version Incompatible After Upgrade
• Meilisearch Disk Usage Keeps Growing / No Space Left on Device
• Meilisearch High Memory Usage