Supabase Management API
/v1/projects/{id}/api-keys/legacy endpoint removal
Deprecated, no dateSubscribe to Supabase Management APIShare
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.
Calls it hits
/v1/projects/{id}/api-keys/legacy
What to use instead of these calls
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.
In 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.
Facts
- API
- Supabase Management API
api.supabase.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Supabase Management API's own pages
Questions
When does this change take effect?
Supabase Management API deprecated /v1/projects/{id}/api-keys/legacy without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Supabase Management API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Supabase Management API 1
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.