Ntfy is a notification service. Ntfy is 1 of the 100+ notification services Apprise supports. Apprise is basically a switchboard for notifications; a one stop shop.
Specifically, ntfy.sh sends to Ntfy's mobile app or to their web notifications page, and you don't need an API key just an arbitrary secret channel name.
In case it's not clear: it's not only for iOS/Android push notifications. It provides a single API to send notifications via a whole bunch of channels (Slack, Telegram etc.).
e.g. I have some code that notifies me in Telegram when something happens. I had to integrate with the Telegram API to do that. That's easy, but what if I want to switch the notification to Slack or something? Or send it to to multiple destinations? My code gets messy pretty quickly. If I switch to using this, I can have multiple scripts that all use the same API, and the choice of destination(s) become some small amount of config in each script.
14 comments
[ 0.18 ms ] story [ 54.4 ms ] threadI wish it supported Jami messages though, but Jami is somewhat hard to do programmatically on Ubuntu, the DBus doesn't seem to cross between Snaps.
https://github.com/caronc/apprise/wiki/Notify_fcm
e.g. I have some code that notifies me in Telegram when something happens. I had to integrate with the Telegram API to do that. That's easy, but what if I want to switch the notification to Slack or something? Or send it to to multiple destinations? My code gets messy pretty quickly. If I switch to using this, I can have multiple scripts that all use the same API, and the choice of destination(s) become some small amount of config in each script.
This would be a nice API to have on simple MCUs.
They all play a roll with merge requests during (GiHub Actions) pipeline testing and code coverage.