Keys / Qdrant

QDRANT_API_KEY

The Qdrant Cloud Database API key your app reads and writes one cluster's collections with.

Starts with
eyJhb
Expires
you choose in days, default 90, or never
API
list, create and delete, with a Cloud Management Key

Get it

Create one on cloud.qdrant.io. The steps aren't recorded yet.

Set it

QDRANT_API_KEY=eyJhb...

The Qdrant MCP server reads it from this variable. The Python and JavaScript clients take it as api_key or apiKey; your app passes it in. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. In the cluster's API Keys section, create a new key with the same permissions and collections. It's shown only once.
  2. Deploy it everywhere that reads QDRANT_API_KEY. A new key can take a few seconds to work; if the first request returns 403, retry.
  3. Check that requests succeed with the new key, then revoke the old one.
  4. Removing the user who created a key doesn't revoke it. Revoke their keys yourself.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16