Cooldown / Rate Limiting for Webhooks and API Messages

Problem:

I use Apple Home to monitor sensors and trigger Pushover notifications via the API when certain thresholds are exceeded (e.g., temperature or humidity). The issue is that while the sensor value remains above the threshold, multiple API calls are made in quick succession, resulting in a flood of redundant notifications for what is essentially the same ongoing event. When the new webhooks feature was announced, I was hoping it would include some form of rate limiting or cooldown functionality to address this – but unfortunately, it doesn't.

Proposed Solution:

Add an optional cooldown/rate limiting feature for webhooks and API calls. This would allow users to define a cooldown period (e.g., 30 minutes) per webhook or application. After a notification is sent, subsequent calls from the same source would be suppressed for the specified duration. This setting should be configurable individually for each webhook or application to accommodate different use cases.