[PAID BOUNTY - $750] Email Threads API

Description

## Bounty Overview Build a thread-first Email Threads API for the warpSpeed app. This bounty introduces a new threaded email experience so users can work with conversations instead of isolated messages. Developers will create API support for listing email threads, opening a thread to view related messages, preserving draft activity inside the correct conversation, and ensuring search/filter behaviour remains consistent with the existing message API. This bounty is part of the warpSpeed OPEN developer bounty programme. ## Reward $750 ## Difficulty Hard ## Main Skills * Node.js * TypeScript * Prisma * API Development * Email Systems * Jest Testing * Swagger / API Documentation ## High-Level Scope The selected developer will build a thread-first email API that supports: * Listing email threads for the authenticated user * Opening a single thread and returning thread metadata with related messages * Grouping filtered/search results by thread * Preserving ownership and access control rules * Including drafts in the correct conversation thread * Excluding archived and deleted messages where required * Updating thread recency when drafts are created, updated, or sent * Ensuring synced Gmail, Outlook, and IMAP emails update thread ordering correctly * Maintaining consistent search and filtering behaviour with the existing messages endpoint * Adding Swagger/API documentation * Adding Jest tests for auth, ordering, filters, drafts, and thread detail behaviour Full technical requirements, submission rules, acceptance criteria, and final implementation expectations are available on the official bounty page. ## View Full Bounty Details & Sign Up To see the full bounty specification and apply, visit: https://warpspeedopen.org/bounties ## How to Claim 1. Open the bounty page. 2. Sign up as a developer. 3. Review the full bounty details and rules. 4. Return to this GitHub issue and comment: "I have signed up and would like to claim this bounty." A maintainer must confirm before work begins. ## Important Rules * Do not start work until a maintainer confirms your claim. * Maximum 3 submission attempts. * Minimum 90% specification match required for consideration. * Payment is made only at 100% completion. * Payment is processed only after the pull request is approved and merged. * First code commit is required at the halfway mark between bounty start and bounty expiration. * Code must be original or properly licensed. * The official bounty page is the source of truth for full requirements, rules, and deadlines.