Uptime Kuma
Uptime Kuma supports Pinglet as a native notification provider: pick it from the notification list, paste your topic URL and API key, and monitor up/down alerts arrive as push.
Setup
In Uptime Kuma, go to Settings → Notifications → Setup Notification and choose Pinglet as the notification type:
| Setting | Value |
|---|---|
| Pinglet Topic URL | https://pinglet.dev/acme/uptime |
| API Key | pinglet_<your key> |
Replace acme/uptime with your namespace and preferred topic name; the topic is created on the 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).
The native provider was merged upstream in August 2026 and ships with the first Uptime Kuma release after 2.5. If Pinglet isn’t in your notification type list yet, use the webhook method below; it produces identical pushes.
Older versions: generic webhook
On an Uptime Kuma without the native provider, choose Webhook as the notification type. Pinglet translates Kuma’s payload server-side via the rewrite parameter:
| Setting | Value |
|---|---|
| Post URL | https://pinglet.dev/acme/uptime?rewrite=uptimekuma |
| Request Body | Preset, application/json (the default) |
| Additional Headers | { "Authorization": "Bearer pinglet_<your key>" } |
uptime_kuma and uptime-kuma are accepted as aliases for the rewrite value.
What you’ll receive
Either method produces the same pushes. 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.