-
Notifications
You must be signed in to change notification settings - Fork 163
Description
Related to an existing integration?
No
Existing integration
No response
Overview
Currently, Apprise API provides a simple fire-and-forget mechanism for sending notifications. While this works well for basic use cases, it becomes limiting in production environments where delivery guarantees, retries, and observability are required.
There is currently no way to:
- determine if a notification was successfully delivered
- track failures per provider (e.g., Telegram, Discord, Email)
- implement retries based on actual delivery status
- correlate a notification request with its result
This makes it difficult to use Apprise as a central notification service in microservice architectures or backend systems that require reliability and monitoring.
This proposal introduces a delivery tracking mechanism with async status retrieval.
Usage example
buider.AddApprise("apprise");
Breaking change?
No
Alternatives
Currently, users must implement their own notification tracking system externally by:
- Wrapping Apprise calls in a custom service
- Logging responses manually (which are often limited)
- Implementing retry logic without knowing actual delivery status
This leads to duplicated effort and inconsistent implementations across projects.
Some users may choose to bypass Apprise entirely and use direct integrations (Telegram API, SMTP, etc.) to gain better control over delivery status.
Additional context
No response
Help us help you
Yes, I'd like to be assigned to work on this item