# /v1/projects/{}/api-keys/legacy is deprecated

Supabase Management API deprecated /v1/projects/{id}/api-keys/legacy without giving a shutdown date yet.

The Supabase Management API endpoint /v1/projects/{id}/api-keys/legacy is deprecated without a shutdown date. Supabase Management API states that this API endpoint will be removed in the future. Once removed, calls to this endpoint fail with an HTTP 404 Not Found response.

## What to use instead

Treat an HTTP 404 response as legacy keys being gone, and switch to using the publishable and secret keys returned by GET /v1/projects/{ref}/api-keys instead.

- API: Supabase Management API (api.supabase.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/v1/projects/{id}/api-keys/legacy`
- Source: [Announcement](https://supabase.com/docs/reference/api/v1-get-project-legacy-api-keys)
- Verified: November 6, 2026, against Supabase Management API's own pages
- Page: https://www.okapi.bot/providers/supabase-management-api/breaking-changes/v1-projects-api-keys-legacy-is-deprecated/

## Supabase Management API's words

> Check whether JWT based legacy (anon, service_role) API keys are enabled. This API endpoint will be removed in the future, check for HTTP 404 Not Found.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent