Uptime Kuma
Uptime Kuma can send its webhook notifications straight to a Pinglet topic — add ?rewrite=uptimekuma to the publish URL and Pinglet translates Kuma’s payload into a proper push. No glue service needed.
Setup
In Uptime Kuma, go to Settings → Notifications → Setup Notification and choose Webhook:
| Setting | Value |
|---|---|
| Post URL | https://app.pinglet.co.uk/acme/uptime?rewrite=uptimekuma |
| Request Body | Preset – application/json (the default) |
| Additional Headers | { "Authorization": "Bearer pinglet_<your key>" } |
Replace acme/uptime with your namespace and preferred topic name — the topic is created on first alert. Hit Test to check the wiring, then attach the notification to your monitors.
Subscribe to the topic in the Pinglet app using the share link from your dashboard (or from the response of a test publish).
What you’ll receive
The monitor’s status maps to the message’s level and priority:
| Monitor status | Title | Level | Priority |
|---|---|---|---|
| Down | <monitor> is down |
error |
urgent — breaks through DND |
| Up | <monitor> is up |
success |
normal |
| Pending | <monitor> is pending |
warning |
normal |
| Maintenance | <monitor> is in maintenance |
info |
normal |
The body is the heartbeat’s reason (200 - OK, connect ECONNREFUSED …), and the card gets up to three badges: the check type, the target host:port, and the response time when available. Scalar context (URL, hostname, duration, retries, ping) lands in the metadata sheet on Pro plans.
Only a down is urgent. Recoveries and routine states arrive as standard notifications, so a flapping monitor won’t hammer through your Do Not Disturb.
uptime_kuma and uptime-kuma are accepted as aliases for the rewrite value.