📦 Scenario

You're integrating with a fictional email provider called FakeMail. It emits webhooks when new emails arrive, and provides a REST API for fetching those emails. Your job is to implement an email processor application.

The way the webhook works is a little bit special. FakeMail doesn’t provide the email data in the webhook payload. Instead, here’s how it’s intended to work:

• On app startup, the client calls the watch endpoint to get the current history_id .
• Then, when FakeMail sends a webhook notification, it will give a latest history_id . This means that all emails up until and including that history_id are ready for processing
• We want to essentially process emails exclusively after the current history id to the latest history id every time we get a webhook notification

✅ Your Task

Implement:

• A webhook receiver (POST /webhook) that fetches new email IDs and processes them via the API
• A GET endpoint (/results/<email_id>) that returns a processed email classification

Processing means:

• Fetching each new email from FakeMail
• Calling the /classify endpoint with that email's contents
• Storing the email_id and its classification result

📬 FakeMail API

Note that you have been provided the request schemas, but not the response. This is intentional - we want to see you play around with the API to figure out how it works.

POST /watch