Support for additional Bark notification parameters (level, volume, call) #4036

New issue

Open

opened 2026-02-28 03:48:59 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:48:59 -05:00

Owner

Originally created by @zhangyongcun on GitHub (Mar 17, 2025).

I have searched through existing issues and could not find any that specifically address adding support for additional Bark notification parameters beyond just the sound parameter.

🏷️ Feature Request Type

Settings

🔖 Feature description

Currently, Uptime Kuma's Bark notification method only supports customizing the sound parameter. However, Bark API actually supports many more useful parameters such as urgency level (level), notification volume (volume), and call functionality (call).

These additional parameters would significantly enhance notification capabilities, especially for critical services monitoring. For example, being able to set level=critical for important services or call=1 to trigger phone calls for severe outages.

✔️ Solution

Add additional configuration fields in the Bark notification setup UI for parameters including but not limited to:

level (with options like active, timeSensitive, critical)
volume (numeric value)
call (boolean toggle)
When sending notifications, these parameters should be appended to the Bark API request URL along with the existing parameters.

The implementation should preserve backward compatibility with existing Bark notification configurations.

❓ Alternatives

I have considered manually adding these parameters to the Bark URL field, but this approach is not user-friendly and might break existing functionality. A proper UI integration would be much more maintainable and accessible to users without deep technical knowledge.

📝 Additional Context

Bark is an iOS notification service that offers rich customization options. Adding support for these additional parameters would make Uptime Kuma's integration with Bark more complete and powerful, allowing for more granular control over how notifications are delivered based on the severity of monitoring events.

Originally created by @zhangyongcun on GitHub (Mar 17, 2025). ### 📑 I have found these related issues/pull requests I have searched through existing issues and could not find any that specifically address adding support for additional Bark notification parameters beyond just the sound parameter. ### 🏷️ Feature Request Type Settings ### 🔖 Feature description Currently, Uptime Kuma's Bark notification method only supports customizing the sound parameter. However, Bark API actually supports many more useful parameters such as urgency level (level), notification volume (volume), and call functionality (call). These additional parameters would significantly enhance notification capabilities, especially for critical services monitoring. For example, being able to set level=critical for important services or call=1 to trigger phone calls for severe outages. ### ✔️ Solution Add additional configuration fields in the Bark notification setup UI for parameters including but not limited to: level (with options like active, timeSensitive, critical) volume (numeric value) call (boolean toggle) When sending notifications, these parameters should be appended to the Bark API request URL along with the existing parameters. The implementation should preserve backward compatibility with existing Bark notification configurations. ### ❓ Alternatives I have considered manually adding these parameters to the Bark URL field, but this approach is not user-friendly and might break existing functionality. A proper UI integration would be much more maintainable and accessible to users without deep technical knowledge. ### 📝 Additional Context Bark is an iOS notification service that offers rich customization options. Adding support for these additional parameters would make Uptime Kuma's integration with Bark more complete and powerful, allowing for more granular control over how notifications are delivered based on the severity of monitoring events.

deekerman added the

feature-request

A:notifications

labels

2026-02-28 03:48:59 -05:00

deekerman commented

2026-02-28 03:49:02 -05:00

Author

Owner

@101br03k commented on GitHub (Mar 30, 2025):

uptime-kuma uses apprise as a notification system.
You should be able to set up Bark using the notification UI in uptime-kuma, otherwise you can check the documentation for how to use Bark: https://github.com/caronc/apprise/wiki/Notify_bark

@101br03k commented on GitHub (Mar 30, 2025): uptime-kuma uses apprise as a notification system. You should be able to set up Bark using the notification UI in uptime-kuma, otherwise you can check the documentation for how to use Bark: https://github.com/caronc/apprise/wiki/Notify_bark