Notification Hub
One HTTP entry point for Telegram and email notifications, with centrally managed routes and credentials.
The problem
One script needs to send a Telegram message; another service needs email. If each integrates separately, both must manage credentials, recipients, and sending code. I wanted those choices in one place: callers submit a message and logical channel, and Notification Hub resolves the destination.
Implemented MVP
A request reaches the FastAPI notification endpoint and passes Bearer authentication. The server resolves the default channel or requested route, then uses Apprise to send through Telegram or email. Recipients and credentials stay on the server, so callers do not need the underlying channel configuration. The MVP also provides a status endpoint and Docker Compose deployment.
My contribution and limits
I defined the API needs, default routes, and VPS constraints; AI assisted code, tests, and deployment documentation. The current design targets personal infrastructure and low-volume use. A single token and in-memory limiter do not constitute a multi-tenant messaging platform, and channel support is not a claim of a measured delivery SLA.