SaaS email template

API key created email — security notification for developer SaaS products

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.

Why API key notifications are often skipped

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.

Key name and scope not shown

"A new API key was created" with no key name or scope context is not useful for audit or security review.

No revoke path in the email

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.

Security emails treated as low priority

API key notifications are often deprioritised in the backlog. else.events makes them easy to add — one event, one template, one rule.

Key name, creator, scope and revoke link — from the event payload

Fire security.api_key_created on every key creation

Your API key service fires the event. The account owner or workspace admin receives the notification immediately.

Key details from the payload

Include key_name, key_scope and created_by in the event payload. The template renders a complete, auditable notification.

Revoke link in the email

Include a revoke_url in the payload. The template renders "Did not authorise this? Revoke the key now."

Managed outside your API key service

Edit notification copy or add a locale without touching the API key service.

Template variables for the API key created email

  • {{ 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 key

Frequently asked questions

Who should receive the API key created notification?
Typically the account owner or workspace admin — whoever has security oversight of the account. Include their email as the recipient in the event payload.
What subject lines work for API key notifications?
"New API key created on your [App] account", "Security notice: API key [key name] was just added", "API key created — was this you?". Include the key name for immediate context.
Should I send this notification even when the owner creates the key themselves?
Yes — for auditability. Some teams send it only for keys created by team members (not the owner), but sending it always creates a consistent audit trail. Your backend controls who receives it.
What should the revoke link do?
It should immediately invalidate the API key. The link should be authenticated or use a short-lived token so the user does not need to log in to revoke.

API key notifications that give account owners control

Key name, creator, scope and one-click revoke — immediate notification when a new key is added.

  • Key details from the event payload
  • One-click revoke link
  • Works for shared accounts and team scenarios