The API Keys page in the Profile section of Signotaur allows you to manage your API keys, including creating new keys, regenerating, or deleting existing ones.

A sortable table displays all existing API keys.
See Also: For comprehensive information about API key lifecycle and rotation strategies, see API Key Lifecycle. For CLI workflows including key rotation, see API Key Management.
To create a new API key, click the Create new API key button. A dialog will appear where you can enter the following details:

After clicking Save, a new API key will be generated and displayed in a dialog. You can copy the key for use with the Signotaur client tool command line. Ensure that you copy and store the key in a safe place, as you will no longer have access to it once the dialog is closed.

To enable or disable a API key, toggle the checkbox in the Enabled column of the API Keys table.
To regenerate an API key, click the Regenerate API key button next to its entry. A dialog will appear with the following options:

After clicking Regenerate, a new API key will be generated and displayed in a dialog. You can copy the key for use with the Signotaur client tool command line. Ensure that you copy and store the key in a safe place, as you will no longer have access to it once the dialog is closed.
Note: Regenerating an API key will render the old key unusable for all future requests.
The Clean up button appears in the API Keys table header when there are expired or revoked keys present. This feature allows you to bulk-delete multiple keys at once rather than removing them individually.
Clicking Clean up opens a dialog with three checkbox options, each displaying a count of matching keys:
Select the categories of keys you want to remove. A warning indicates that this action is permanent and cannot be undone. Click Delete to proceed with the removal.

To permanently remove an API key, click the Delete button next to its entry. A confirmation dialog will appear to confirm the deletion.
Note: Deleting an API key will revoke its access and render it unusable for all future requests.