# Get downtime alerts in ntfy

> Point a YoPingMe webhook at an ntfy topic and get push alerts with zero glue code. One caveat about topic names is worth reading first.

Published: 2026-08-07 | Canonical: https://yoping.me/integrations/ntfy

## How do I get YoPingMe alerts in ntfy?

Add a webhook alert channel in YoPingMe with your ntfy topic URL as the
destination. That is the whole recipe: ntfy turns any POST body into a push
notification, and YoPingMe's webhook sends a JSON POST for every alert. No
relay, no code.

1. Pick a topic and subscribe to it in the ntfy app:
   `https://ntfy.sh/<your-topic>`. Topic names are explained below - do not
   use a guessable one.
2. In the YoPingMe dashboard, add an alert channel of type webhook and
   paste the topic URL.
3. Attach the channel to a monitor and send a test alert, or curl the
   topic to confirm your subscription works:

```bash
curl -d '{"event":"down","monitor":"my site","target":"https://example.com"}' \
  https://ntfy.sh/<your-topic>
```

## What the notification looks like

The raw JSON payload, as text. Functional, not pretty: you will see
`"event":"down"`, the monitor name, the target, and the cause in one line.
If you want titles, colors, and priorities instead, the pattern in
[the Discord recipe](/integrations/discord) adapts to ntfy's headers with
a few lines changed.

## Pick a topic name like a password

ntfy.sh topics are open by default. Anyone who knows the topic name can
read your alerts and post to them - there is no signup and no ACL on the
free public server. Two sane options:

- A long random topic name, for example `yp-alerts-x7k2m9q4w1`. Treat it
  like a password.
- A self-hosted ntfy server with auth enabled, if your alerts should not
  ride on a public service at all.

## Delivery guarantees

The webhook contract is documented in full in
[the Discord recipe](/integrations/discord#the-webhook-payload). The short
version: delivery times out after 10 seconds, failed sends are retried up
to 5 attempts over about 10 minutes of doubling backoff, and delivery is
at-least-once - duplicates carry the same `idempotency_key`.