Skip to main content
Source: Cross-cutting guide — references equa-server/modules/notifications/ and the Notifier interface used across endpoint handlers

​
Notification Endpoints

The Equa notification system handles email delivery for authentication events, member invitations, and other platform communications. This is an internal service — there are no direct user-facing notification API endpoints.

​
How Notifications Work

Notifications are sent server-side through a Notifier function injected into endpoint handlers. When an action requires an email (e.g., invitation, password reset, magic link), the handler calls notify(userId, options) internally.

​
Notification Triggers

The following actions trigger email notifications:

​
Email Transport

The email transport is configured via environment variables: In development mode (EMAIL_TRANSPORTER=dev), emails are saved to a local temp/ folder instead of being sent. Magic link emails include:
  • A secure sign-in URL valid for 15 minutes
  • The link is single-use (marked as used after verification)
  • In dev mode, the token is included in the API response for testing

​
Template System

Email templates are managed through the notification module (modules/notifications). Templates use Handlebars for variable interpolation. The magic link template is located at:

​
Integration Notes

  • There is no REST endpoint to send arbitrary notifications
  • All notification sending is triggered by server-side business logic
  • Email verification has a cooldown (EMAIL_VERIFICATION_LIMIT_SECONDS, default 1800s)
  • The Notifier abstraction supports multiple transport backends