ntfy¶
ntfy.sh is a simple, open-source push notification service. Subscribe to a topic on your phone or desktop and receive alerts the moment something goes down — no account required for public topics, and fully self-hostable.
How it works¶
Wanepia POSTs a plain-text message to your ntfy topic URL. ntfy relays it to all subscribers on that topic (mobile app, browser, or CLI).
Setup¶
- Install the ntfy app on your phone (iOS / Android)
- Subscribe to a topic name of your choice (e.g.
my-infra-alerts) - Your topic URL is
https://ntfy.sh/my-infra-alerts
For private topics, generate an access token in the ntfy web UI and pass it as token.
For self-hosted ntfy, use your own server URL (e.g. https://ntfy.example.com/my-alerts).
Adding an ntfy channel¶
- Open a check's notification panel
- Click Add channel → select ntfy
- Enter your topic URL and optional token
- Click Add
Config fields¶
| Key | Required | Description |
|---|---|---|
url |
Yes | Full ntfy topic URL including scheme and topic name |
token |
No | Bearer token for protected topics |
Notification format¶
Wanepia sets ntfy headers to give rich metadata:
| Header | Down | Degraded | Up / recovery |
|---|---|---|---|
Title |
payments-api — down |
payments-api — degraded |
payments-api — up |
Priority |
urgent |
high |
low |
Tags |
skull |
warning |
white_check_mark |
Body (plain text):
The urgent priority makes the notification break through Do Not Disturb on iOS and Android.
Self-hosted ntfy¶
Point url at your own server:
Self-hosted ntfy supports the same API, so no other changes are needed.
Troubleshooting¶
- 403 Forbidden: the topic is access-controlled and you haven't provided a valid
token. - Topic not found (404): the topic URL is incorrect.
- Wanepia expects a
2xxresponse. Non-2xx counts as failure and triggers retries. - Use
wnp notify logsto inspect delivery attempts.