All API key events include the standard actor, targets, context, and metadata fields. The schemas below show event-specific fields.
api_key.create
Records when a new API key is created for a project.Triggered When
User creates an API key via the “Create API Key” form in a project’s API keys page.Event Schema
string
required
api_key.createarray
required
string
required
Page route where API key was created:
/projects/[projectId]/api-keys/newstring
ISO 8601 timestamp when key expires (null if no expiration set)
string
Comma-separated list of allowed IP addresses/CIDR blocks (null if no restrictions)
Example Event
api_key.update
Records when an API key’s configuration is modified (name, expiration, or IP restrictions).Triggered When
User updates an API key’s settings via the edit forms on the API key details page (name, expiration date, or IP address restrictions).Event Schema
string
required
api_key.updatearray
required
string
required
JSON string containing changed fields with
from and to values. Possible fields: name, expiration_date, ip_addressesExample Event
api_key.update_status
Records when an API key’s status changes between active and paused states.Triggered When
User activates or pauses an API key via the status action buttons on the API key details page. This event is NOT triggered for revocations (seeapi_key.revoke).
Event Schema
string
required
api_key.update_statusarray
required
string
required
Previous status (
active or paused)string
required
New status (
active or paused)Example Event
api_key.revoke
Records when an API key is permanently revoked (cannot be reversed).Triggered When
User revokes an API key via the “Revoke” action button on the API key details page. Revoked keys cannot be reactivated.Event Schema
string
required
api_key.revokearray
required
object
required
Empty object (no event-specific metadata)
Example Event
api_key.view_details
Records when a user views an API key’s detailed configuration page.Triggered When
User navigates to an API key’s details page to view its configuration, statistics, and usage history.Event Schema
string
required
api_key.view_detailsarray
required
string
required
Page route where details were viewed:
/projects/[projectId]/api-keys/[apiKeyId]Example Event
api_key.list
Records when a user views the list of API keys for a project.Triggered When
User navigates to a project’s API keys page to view all keys in that project.Event Schema
string
required
api_key.listarray
required
string
required
Page route where list was viewed:
/projects/[projectId]/api-keysExample Event
api_key.delete
Records when an API key is permanently deleted from a project.Triggered When
User deletes an API key via the delete action on the API key details page or list view.Event Schema
string
required
api_key.deletearray
required
string
required
Page route where API key was deleted:
/projects/[projectId]/api-keysExample Event
api_key.list_usage
Records when a user views or filters the usage history for an API key.Triggered When
User views the usage section on an API key’s details page, or applies filters (date range, classification, pagination) to the usage results.Event Schema
string
required
api_key.list_usagearray
required
string
required
Page route where usage was viewed:
/projects/[projectId]/api-keys/[apiKeyId]string
ISO 8601 timestamp for usage query start date (null if not filtered)
string
ISO 8601 timestamp for usage query end date (null if not filtered)
string
Filter for scan result classification:
safe, unsafe, unknown, or null if not filteredstring
required
Current page number (1-indexed)
string
required
Number of results per page
string
required
Total number of usage records matching filters

