Closed Bluel0la closed 1 week ago
Emails should be integrated into one service
On it Sir
Your APIs must be versioned. You must at all times follow REST API naming conventions and best practices; please study the included resources REST API naming conventions API Best practices
@markessien done please can you review
@pesova it has been implented
Acceptance Criteria
Description:
Implement a unified email notification service to handle email notifications for account verification for new users and magic-link sign-ins. This service should manage all email-related functionalities.
Purpose:
To streamline and centralize the email notification process for account verification and magic-link sign-ins, ensuring consistency and ease of maintenance.
Acceptance Criteria:
Automated Email Notification System:
User Preferences:
Email Delivery:
Email Templates:
Expected Outcome:
Requirements:
Endpoints:
User Registration:
Description: Register a new user and send an account verification email.
USER REGISTRATION [POST] /api/v1/auth/register
Response (Success)
Response (Error)
Magic Link Sign-In:
Description: Send a magic link email for user sign-in.
MAGIC-LINK SIGN-IN [POST] /api/v1/auth/magic-link
Response (Success)
Response (ERROR)
Testing:
Example Email Templates:
Account Verification Email:
Subject: Verify Your Account
Body: Click the link below to verify your account:
Magic Link Email:
Subject: Sign In with Magic Link
Body: Click the link below to sign in:
Corresponding database Tables for the implementation of the endpoints: