Update to API Key Settings
We have just released an improvement to our API Key Settings, to support multiple private API keys.
Details of the changes:
- We now support multiple name private API keys, which makes it easier to track which keys are used and how. Those can be used for custom API integrations or by developers.
- The private API keys can no longer be accessed from the user interface, but only once when they are created
- The Legacy private API key is still valid for now, and should be kept configured in your extension until further notice
Security recommendation: We recommend assigning individual private keys to the people/developers/systems that need full access to your clerk API.
