- Pick a topicChoose a hard-to-guess topic name and subscribe to it in the ntfy app, for example https://ntfy.sh/acme-alerts-7f3k9.
- Create a token for protected topics (optional)If the topic requires sign-in, create an access token starting with tk_ in your ntfy account.
- Add the destinationIn Integrations, choose "Set up ntfy", enter the Topic URL and, if needed, the Access token (optional).
- Save and testChoose "Add destination", then "Send test", and check the ntfy app.
ntfy is an open-source push notification service. Uptime Tracker publishes each alert to one ntfy topic, on ntfy.sh or on your own ntfy server. ntfy destinations are available on the Starter and Team plans.
Before you start
- A workspace on Starter or Team.
- The ntfy app on your phone or desktop, subscribed to the topic you will use.
- A self-hosted server must be reachable from the internet over HTTPS at its own host name. Servers on private networks or served under a sub-path (such as
https://example.com/ntfy/) are not supported.
Choose the topic URL
The Topic URL is the HTTPS address of the server plus a single topic name of up to 64 letters, digits, - or _, for example https://ntfy.sh/acme-alerts-7f3k9. On the public ntfy.sh server anyone who knows a topic name can read it, so use a long, hard-to-guess name, or a protected topic.
Subscribe to the same topic in the ntfy app before you test.
Protected topics: create an access token
If your topic requires sign-in, create an access token for a user that may publish to it. In the ntfy web app, open your account settings and create one under Access tokens; on a self-hosted server you can also run ntfy token add <username>. Tokens start with tk_. Leave the token field empty for open topics.
Add it in Uptime Tracker
- Go to Integrations, find ntfy and choose Set up ntfy.
- Enter a Name and the Topic URL.
- For a protected topic, paste the token into Access token (optional). It is stored encrypted and never shown again.
- Choose Add destination, then Send test.
What you receive
Down, reminder and escalation alerts are published with ntfy's highest priority (5, "urgent"), which makes the app ring and vibrate. Recoveries, acknowledgements and tests use the default priority (3).
Troubleshooting
- "The endpoint is not a valid ntfy URL": the URL must be
https://, and have exactly one path segment: the topic name. - "Destination must be a publicly routable HTTPS endpoint": your server resolves to a private address or does not use HTTPS.
- HTTP 401 or 403 in the Deliveries tab: the topic is protected and the token is missing, wrong or lacks write access. The destination is disabled with a reason; add a new destination with a valid token.
- "The referenced secret is not a valid ntfy credential": access tokens are
tk_followed by 29 letters and digits. Passwords are not accepted.
Frequently asked questions
Can I use my self-hosted ntfy server?
Yes, if it is reachable from the internet over HTTPS at its own host name. Servers on private networks or under a sub-path are not supported.
Do I need an ntfy account?
Not for open topics. For protected topics, create an access token starting with tk_ and enter it in the destination.
Which plan includes ntfy?
Starter and Team.
