How do I keep SeleID API keys safe?

Identify the workspace, project and operations the integration needs. If key creation is available, create the least privileged key you can use. Store it in your secrets manager and configure rotation. If a key appears in a public repository or browser bundle, revoke or rotate it and review its recent use.

If a key appears in a public repository or browser bundle, revoke or rotate it and review its recent use. Identify the workspace, project and operations the integration needs. If you need help, include the product you were using and the step that failed. Keep passwords, one-time codes and secret keys private.

Keep any SeleID server API key in the environment that runs your server. Use separate keys for different projects or environments where supported and give each the smallest necessary permissions. Consult the product documentation and console to confirm that key creation is available for your account.