Implement Newsletter Subscription Endpoint (Get Notified)

[yusuftomilola]

We need to implement a newsletter subscription endpoint that allows users to subscribe to our mailing list and receive notifications. The backend implementation must align with the existing frontend newsletter component's type definitions and API contract.

🎯 Objective

Create a production-ready newsletter subscription endpoint:

• POST /newsletter/subscribe - Subscribe users to the newsletter

📂 Context

The frontend newsletter component has already been implemented. Please review:

• Newsletter Component: /frontend/components/ui/newsletter
• Type definitions: Check for newsletter-related types/interfaces
• Form component: Review the newsletter form structure
• Validation schemas: Check frontend validation rules
• API service files: Look for expected request/response structures

✅ Acceptance Criteria

1. Newsletter Subscription Endpoint (POST /newsletter/subscribe)

• Accept email address from user
• Validate email format
• Check for duplicate subscriptions (prevent re-subscribing)
• Store subscriber information in database
• Add subscription timestamp
• Generate unique subscription ID/token
• Return appropriate success/error responses
• Match frontend type expectations exactly

2. Data Validation

• Email format validation
• Sanitize input to prevent XSS/injection attacks
• Handle empty/null values gracefully
• Validate against disposable email addresses (optional but recommended)
• Rate limiting to prevent spam (bonus points!)

3. Database Schema

• Create Newsletter or Subscriber entity
• Include fields: email, subscribedAt, isActive, unsubscribeToken
• Add unique constraint on email field
• Include soft delete capability (for unsubscribes)
• Add indexes for performance

4. Optional Features (Bonus Points!)

• Send confirmation email to subscriber
• Double opt-in mechanism (send verification link)
• Unsubscribe endpoint (POST /newsletter/unsubscribe)
• GDPR compliance fields (consent timestamp, IP address)
• Email service integration (SendGrid, Mailchimp, etc.)

5. Testing & Documentation

• Server runs without errors
• Endpoint tested with Postman/Thunder Client/similar tool
• Include screenshots of successful API calls in PR
• Test duplicate subscription handling
• Test invalid email formats
• Add error handling for all scenarios
• Write basic unit tests (bonus points!)
• Update API documentation/Swagger if applicable

🛠️ Technical Requirements

Required Technologies

• Framework: NestJS
• Database: PostgreSQL with TypeORM
• Validation: class-validator & class-transformer
• Email: nodemailer,

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

GM maintainer,
I would implement a production-ready Newsletter Subscription API at POST /newsletter/subscribe that exactly matches the frontend newsletter component’s request/response contract, enforces strong validation (email, duplicates, sanitization), persists subscribers with timestamps and a unique token, and includes lightweight anti-spam protection (rate limiting + optional disposable email blocking).

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Obiajulu-gif to this issue.

[JerryIdoko]

@JerryIdoko has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi there! 👋

I would like to work on this issue. I’ve reviewed the requirements and the existing frontend context, and I’m comfortable with the stack (NestJS, TypeORM, PostgreSQL).

Here is my brief plan for the implementation:

Database: Create the Subscriber entity with the required fields (email, subscribedAt, unsubscribeToken) and a unique constraint on the email.

DTOs: Implement the CreateSubscriptionDto using class-validator to handle email validation and sanitization.

Service: Implement the subscribe logic to handle duplicates gracefully and store the user data.

Controller: Expose the POST /newsletter/subscribe endpoint aligning with the frontend API contract.

Please assign this to me, and I can get started immediately.

Best regards, Kevin

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JerryIdoko to this issue.

[Bappa-Kamba]

@Bappa-Kamba has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bappa-Kamba to this issue.

[Villarley]

@Villarley has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hey team i'm Santiago Villarreal Full stack and smart contract dev in stellar ecosystem. would love to tackle on this one!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Villarley to this issue.

[Agbeleshe]

@Agbeleshe has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello, I am very interested in working on Issue #442 and would really appreciate being assigned to implement the newsletter subscription endpoint for ManageHub. This feature is an important bridge between the existing frontend newsletter component and a production-ready backend service, and I am confident I can deliver a clean, secure, and well-aligned implementation. I will carefully review the current frontend newsletter components, validation rules, and API expectations to ensure the backend contract matches exactly, avoiding integration friction.

If assigned, I will build a robust POST /newsletter/subscribe endpoint in NestJS with proper email validation, duplicate prevention, sanitized inputs, and a PostgreSQL-backed subscriber entity using TypeORM. I will include unique constraints, timestamps, and unsubscribe token support, and I can also extend this with optional features such as rate limiting, double opt-in, and an unsubscribe endpoint if desired. I will test all scenarios (success, duplicates, invalid emails), add basic unit tests, and update documentation where applicable. I would genuinely appreciate the opportunity to contribute this feature and help strengthen ManageHub’s user engagement and reliability.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Agbeleshe to this issue.

[emperorsixpacks]

@emperorsixpacks has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I'm Andrew, a fullstack developer with extensive experience in building robust and efficient systems. I would love to contribute to this issue and provide a high-quality solution. I'm available to start immediately.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @emperorsixpacks to this issue.

[drips-wave]

Congratulations, @Bappa-Kamba! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

🧑‍💻 @Bappa-Kamba: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊