API tools #658

New issue

Open

opened 2026-05-07 00:26:21 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:26:21 +02:00

Owner

Originally created by @osering on GitHub (Nov 6, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/938

💡 Idea
There is possibility to send and receive notifications through android intents (for instance ,in closedsource Macrodroid, and opensource Automate) in CLI (outside of app, GUI), but no possibility to subscribe/unsubscribe to topics, like in other OS
https://docs.ntfy.sh/subscribe/cli/
https://docs.ntfy.sh/subscribe/api/

It also could be quite easily done, if all subscriptions would be put in some xml config file (not in sqlite db) in io.hackel.ntfy/shared_prefs/ (like other android apps implement configs), possibly in existing file MainPreferences.xml of SubscriberService.xml (both of which looks underused) where it could be edited by (shell) script (and later - probably, by some specific ntfy command/implementation).
So user without hassle could add/remove subscription topics on the fly and it would sync (maybe reload required) with topics seen in apps GUI.

💻 Implementation
Should possibly be added in Android app, by changing place where info about active/subscribed topics is stored - doing it in plain text xml config file, not db.

Originally created by @osering on GitHub (Nov 6, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/938 :bulb: **Idea** There is possibility to send and receive notifications through android intents (for instance ,in closedsource Macrodroid, and opensource Automate) in CLI (outside of app, GUI), but no possibility to subscribe/unsubscribe to topics, like in other OS https://docs.ntfy.sh/subscribe/cli/ https://docs.ntfy.sh/subscribe/api/ It also could be quite easily done, if all subscriptions would be put in some xml config file (not in sqlite db) in io.hackel.ntfy/shared_prefs/ (like other android apps implement configs), possibly in existing file MainPreferences.xml of SubscriberService.xml (both of which looks underused) where it could be edited by (shell) script (and later - probably, by some specific ntfy command/implementation). So user without hassle could add/remove subscription topics on the fly and it would sync (maybe reload required) with topics seen in apps GUI. :computer: **Implementation** Should possibly be added in Android app, by changing place where info about active/subscribed topics is stored - doing it in plain text xml config file, not db.