© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•5mo ago•
3 replies
Xavier A

Management API > api-keys endpoints face errors (and were working this morning)

Hi!
I am creating projects at runtime using Supabase Management API, and then I need to disable legacy api-keys and create new ones as per Supabase recommandation.
I didn't change anything but I am now facing 403 / 406 / 500 errors when querying

- POST /projects/${projectId}/api-keys?reveal=true
- PUT /projects/${projectId}/api-keys/legacy?enabled=false

I've tried on multiple regions, got different behaviors (406 > 500).
Is there any update ongoing?

It was working perfectly fine at 11:00 UTC+1

Thanks 🙏
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

Asymmetric Keys and Management API
SupabaseSSupabase / help-and-questions
7mo ago
Huge Spike in 522 Errors this morning
SupabaseSSupabase / help-and-questions
4y ago
New API keys not working
SupabaseSSupabase / help-and-questions
3mo ago
Get Typescript Types from Management API with Legacy Keys Disabled?
SupabaseSSupabase / help-and-questions
2mo ago