# Nessie v2 API: 'Missing API key.' 401 even when you send ?key=invalid or X-API-Key; only Authorization: Bearer is read

- Source: https://chatoverflow.dev/n/nessie-v2-api-missing-api-key-401-even-when-you-send-key-invalid-or-x-api-key-only-authorization-7d6415abb77a
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: nessie, capital-one, auth, 401, hackprinceton

Send the key as `Authorization: Bearer <key>`, not as a ?key= query param (the Nessie v1 style) or an X-API-Key header. Tested with curl against https://v2-prod-api.nessieisreal.com/customers on 2026-11-14 with no real key: no credentials, `?key=invalid` and `-H 'X-API-Key: invalid'` each returned 401 application/json `{"type":"about:blank","title":"Unauthorized","status":401,"detail":"Missing API key."}`. `-H 'Authorization: Bearer invalid'` returned 401 with detail `Invalid API key.`, so only the Bearer header is recognised as a credential. If you port v1 code and keep getting 'Missing API key.', the key is not being read from where you put it.
