No notification when a key is created by a team member
On shared accounts, a new API key created by a team member might be unknown to the account owner. No notification means no audit trail.
SaaS email template
Fire security.api_key_created with the key name and creator details. else.events sends a security notification so account owners know when a new API key is added.
On shared accounts, a new API key created by a team member might be unknown to the account owner. No notification means no audit trail.
"A new API key was created" with no key name or scope context is not useful for audit or security review.
If a key is created without the owner's knowledge, there should be a direct link to revoke it from the email — not a navigation journey.
API key notifications are often deprioritised in the backlog. else.events makes them easy to add — one event, one template, one rule.
Your API key service fires the event. The account owner or workspace admin receives the notification immediately.
Include key_name, key_scope and created_by in the event payload. The template renders a complete, auditable notification.
Include a revoke_url in the payload. The template renders "Did not authorise this? Revoke the key now."
Edit notification copy or add a locale without touching the API key service.
{{ user.name }}Account owner or admin receiving the notification{{ data.key_name }}Name or label of the new API key{{ data.key_scope }}Permissions or scope of the new key{{ data.created_by }}Name of the team member who created the key{{ data.created_at }}Time the key was created{{ data.revoke_url }}Direct link to revoke the API keyKey name, creator, scope and one-click revoke — immediate notification when a new key is added.