TypeScript type generation fails after migrating to new publishable and secret keys

[atej]

Running npx supabase gen types typescript --project-id xxx > ./src/supabase.types.ts

results in the following:

Supabase CLI 2.31.8

HTTP GET: https://api.supabase.com/v1/projects/xxx/types/typescript?included_schemas=public
failed to retrieve generated types: {"message":"{"message":"Legacy API keys are disabled","hint":"Your legacy API keys (anon, service_role) were disabled on xxx. Re-enable them in the Supabase dashboard, or use the new publishable and secret API keys."}"}

---

What are the changes required to get type generation working again?

[jrmoynihan]

Same problem. Didn't see this duplicate until I generated my ticket from the CLI.

[eybel]

Can't re-generate types after this migration.

`failed to retrieve generated types: {"message":"{\"message\":\"Legacy API keys are disabled\",\"hint\":\"Your legacy API keys (anon, service_role) were disabled on 2025-07-22T16:28:01.624439+00:00. 
Re-enable them in the Supabase dashboard, or use the new publishable and secret API keys.\"}"}
Try rerunning the command with --debug to troubleshoot the error.`

[jeromevvb]

Same if i am trying to get the types from the dashboard - the thing i cant re-enable these keys since i switched to the new API keys

[eybel]

any news on this? I cant download my types

[MegaBurek]

I can confirm that the following endpoint is failing to produce types after the new JWT signing keys migration
https://api.supabase.com/v1/projects/project-id/types/typescript?included_schemas=public, storage, graphql_public

Error message:
failed to retrieve generated types: {"message":"{\"message\":\"Legacy API keys are disabled\",\"hint\":\"Your legacy API keys (anon, service_role) were disabled on 2025-07-25T09:21:22.465391+00:00. Re-enable them in the Supabase dashboard, or use the new publishable and secret API keys.\"}"}

I also noticed in the headers that the bearer token seems to be using the old anon key rather than the new publishable key, if I am correct
authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IjNlNjE5Yz...

[sweatybridge]

We have identified the problem and will be releasing a server side fix soon.