Skip to main content
The ntfy integration publishes UptimeKit notifications to an ntfy topic. It works with ntfy.sh and publicly reachable self-hosted ntfy servers.

​
Configuration

FieldDescriptionRequired
Server URLThe root URL of ntfy.sh or your self-hosted ntfy server.Yes
TopicThe topic subscribed to by your ntfy clients.Yes
Access tokenA Bearer token with permission to publish to a protected topic.No
PriorityThe notification priority sent to ntfy.Yes
TagsComma-separated ntfy tags or emoji shortcodes.No
1

Choose and subscribe to a topic

Choose a difficult-to-guess topic containing letters, numbers, underscores, or dashes, then subscribe to it from your ntfy app. Topic names can contain up to 64 characters.
2

Protect the topic (recommended)

If your ntfy server has access control enabled, create an access token that can publish to the topic. UptimeKit sends it as a Bearer token.
3

Configure UptimeKit

  1. Open Integrations in the UptimeKit dashboard.
  2. Add ntfy.
  3. Enter the server URL, topic, and optional access token, priority, and tags.
  4. Choose the events and monitors that should use this notification.
  5. Save the integration, then use Test to send a test notification.

​
Supported events

The integration can send notifications for incident creation, updates, acknowledgement, comments, merges, resolution, deletion, and expiring SSL certificates. Incident and monitor notifications include a link back to UptimeKit where applicable.
In production, the ntfy server URL must resolve to a public address. This prevents notification configuration from making requests to private infrastructure.