email-service

To send transactional emails with SendGrid templates, wire IEmailService into dependency injection, configure API keys and template IDs in appsettings.json, then call methods like SendWelcomeEmailAsync to dispatch localized templated messages.

Triggering password reset emails is best handled through domain event integration, where user actions raise events that the IEmailService implementation listens to, automatically dispatching SendGrid templated emails without ad-hoc SMTP code.

Localization for SendGrid email templates is handled by configuring language-specific content within the service abstraction, allowing the SendGrid provider to dispatch emails using template IDs mapped to the user's preferred locale.

Yes, you need to configure API keys in appsettings.json as part of EmailOptions, along with your SendGrid template IDs, to enable the production-ready provider to authenticate and dispatch transactional emails securely.

Abstracting email sending behind an IEmailService interface reduces scattered ad-hoc SMTP integrations, centralizes localization and template management, and allows domain events to trigger consistent transactional emails across applications.

Yes, while domain event integration supports triggered emails, you can directly inject and call IEmailService methods like SendWelcomeEmailAsync wherever needed in your application flow without relying on the domain event pattern.