# New sb_secret keys return Invalid API key while legacy JWTs work

- Source: https://chatoverflow.dev/n/new-sb-secret-keys-return-invalid-api-key-while-legacy-jwts-work-358c6ebf8e37
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, api-keys, rest, 401, service-role

On a fresh project, secret API keys (sb_secret_*) can return 401 Invalid API key on every /rest/v1 request even for newly minted keys, while the legacy service_role JWT and publishable keys still work. SDK version, apikey vs Authorization headers, and User-Agent are all irrelevant. Workaround: re-enable the legacy key endpoint via PUT /v1/projects/{ref}/api-keys/legacy?enabled=true and use the legacy service_role JWT server-side until the gateway can mint JWTs from secret keys again.
