Creating an API Key
API key management requires the
admin role. Only administrators can create, rotate, and disable API keys.From the UI
Navigate to Admin > API Keys and click Create API Key. Provide a name, description, and select the scopes the key should have access to.From the API
Using an API Key
Pass the API key in theX-API-Key header with every request:
Scopes
Each API key is restricted to a set of scopes that control which endpoints it can access:
A request to an endpoint outside the key’s scopes returns
403 Forbidden:
Key Rotation
Rotate an API key to generate a new secret without changing the key ID. This allows you to update integrations gradually with an optional grace period for the old key.During the grace period, both the old and new API keys are accepted. This gives you time to update all integrations before the old key expires.
Listing API Keys
List all API keys with optional search:key_prefix is shown.
Disabling an API Key
Disable a key to immediately revoke access:Key Status
Best Practices
- Use scoped keys — Only grant the minimum scopes needed for each integration
- Set expiration dates — Do not create keys that never expire; use the
expires_in_daysparameter - Rotate regularly — Use the rotation endpoint with a grace period to update keys without downtime
- Monitor usage — Check
last_used_atin the admin panel to identify unused keys for cleanup - Use descriptive names — Name keys after the integration they serve (e.g., “SOAR Integration”, “CI Pipeline”)
- Store securely — Use a secrets manager (Azure Key Vault, HashiCorp Vault) rather than embedding keys in code
