mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1010] Overseerr JSON Fails with webook field email in payload body #706
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#706
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @undaunt on GitHub (Jan 24, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1010
🐞 Describe the bug
When attempting to test notifications from Overseerr to ntfy, if the line
"email": "{{notifyuser_email}}",is included in the webhook template, ntfy responds with an error that email notifications are not enabled.💻 Components impacted
ntfy server
💡 Screenshots and/or logs
Error sending webhook notification {"type":"TEST_NOTIFICATION","subject":"Test Notification","errorMessage":"Request failed with status code 400","response":{"code":40001,"http":400,"error":"e-mail notifications are not enabled","link":"https://ntfy.sh/docs/config/#e-mail-notifications"}}🔮 Additional context
If I modify the template from the following:
to this
then it works without issue. For reference, my URL is https://ntfy.domain.com/?auth=bearertoken
@wunter8 commented on GitHub (Jan 24, 2024):
It sounds like you didn't enable email notifications on your server
https://docs.ntfy.sh/config/#e-mail-notifications
@undaunt commented on GitHub (Jan 24, 2024):
@wunter8 I'm attempting to post a JSON webhook to ntfy from Overseerr, nothing to do with emails. The templated email line above refers to the fact that my user record in Overseerr has an email. That's why I'm wondering if there's something in the code that makes ntfy think I want to send/receive an email when I do not, based on the JSON payload field name.
@wunter8 commented on GitHub (Jan 24, 2024):
Since you're including an "email" field in the JSON body, ntfy thinks you want to forward the notification to that email address
I would expect both of the JSON bodies you posted above to fail, though, because right now ntfy will reject unknown fields (such as notification_type, username, avatar, etc.)
@binwiederhier commented on GitHub (Feb 5, 2026):
This is not a bug, but rather wrong usage. If you are posting directly to the base URL, ntfy will interpret the body as JSON publishing and that will interpret the email field, see https://docs.ntfy.sh/publish/#publish-as-json