starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: Add support for editing the notification JSON payload #3071

New Issue
Open
opened 2026-04-25 00:13:26 +02:00 by adam · 2 comments
adam commented 2026-04-25 00:13:26 +02:00
Owner
Copy Link
Copy Source

Originally created by @badnetmask on GitHub (Nov 4, 2025).

Type of Enhancement

None

Describe the Feature/Enhancement

This is basically a follow-up on #3755.

The notification system currently enabled in Audiobookshelf expects that you have an Apprise API server running somewhere. While I understand this is a design decision by the developers, it might be redundant for some people who, like me, already have an API ready to be used somewhere else.

I would like to request a bit more flexibility on how notifications are configured, like for example being able to customize the JSON payload.

Why would this be helpful?

Some people might want to use other notification APIs like Pushover, for example.

Currently I am able to kind of getting it working by setting the notification URL to https://api.pushover.net/1/messages.json?user=<CODE>&token=<CODE>, which allows me to receive a broken message that has the correct title, but the wrong body (the body is basically the unformatted JSON of the title element).

Future Implementation (Screenshot)

Unsure how this could look.

Audiobookshelf Server Version

v2.30.0

Current Implementation (Screenshot)

No response

Originally created by @badnetmask on GitHub (Nov 4, 2025). ### Type of Enhancement None ### Describe the Feature/Enhancement This is basically a follow-up on [#3755](3755). The notification system currently enabled in Audiobookshelf expects that you have an [Apprise API server](https://github.com/caronc/apprise-api) running somewhere. While I understand this is a design decision by the developers, it might be redundant for some people who, like me, already have an API ready to be used somewhere else. I would like to request a bit more flexibility on how notifications are configured, like for example being able to customize the JSON payload. ### Why would this be helpful? Some people might want to use other notification APIs like [Pushover](https://pushover.net/api), for example. Currently I am able to _kind of_ getting it working by setting the notification URL to `https://api.pushover.net/1/messages.json?user=<CODE>&token=<CODE>`, which allows me to receive a broken message that has the correct title, but the wrong body (the body is basically the unformatted JSON of the title element). ### Future Implementation (Screenshot) Unsure how this could look. ### Audiobookshelf Server Version v2.30.0 ### Current Implementation (Screenshot) _No response_
adam added the enhancement label 2026-04-25 00:13:26 +02:00
adam commented 2026-04-25 00:13:26 +02:00
Author
Owner
Copy Link
Copy Source

@Vito0912 commented on GitHub (Nov 4, 2025):

I think this has been discussed quite often, that Apprise will probably be the only supported service. I am just a contributor and can't speak for what the maintainers say. But on Discord it was made somewhat very clear that Apprise will be the only supported service as it has built-in support for most things. Also, it's already possible with Apprise from what I read in issue 3755

Pinging @advplyr for an opinion on whether this should be closed or left open.
The correct issue link is https://github.com/advplyr/audiobookshelf/issues/3755

@Vito0912 commented on GitHub (Nov 4, 2025): I think this has been discussed quite often, that Apprise will probably be the only supported service. I am just a contributor and can't speak for what the maintainers say. But on Discord it was made somewhat very clear that Apprise will be the only supported service as it has built-in support for most things. Also, it's already possible with Apprise from what I read in issue 3755 Pinging @advplyr for an opinion on whether this should be closed or left open. The correct issue link is https://github.com/advplyr/audiobookshelf/issues/3755
adam commented 2026-04-25 00:13:26 +02:00
Author
Owner
Copy Link
Copy Source

@badnetmask commented on GitHub (Nov 4, 2025):

I understand that Apprise API might be the only specifically supported method. I'm not asking to have direct support for the Pushover API. As long as one can write their custom JSON payload, instead of having a fixed form like today, that should be sufficient for most advanced users.

I actually edited the title to make it generic.

@badnetmask commented on GitHub (Nov 4, 2025): I understand that Apprise API might be the only specifically supported method. I'm not asking to have direct support for the Pushover API. As long as one can write their custom JSON payload, instead of having a fixed form like today, that should be sufficient for most advanced users. I actually edited the title to make it generic.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3071
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?