Skip to content

Feeds

Every account exposes an Atom XML feed of incidents at a single URL:

https://api.uptimemonitoring.com/feed/{token}/rss

The path segment is feed (singular, not /api/v1/feeds/...). The body is Atom XML even though the path ends in /rss — the suffix is preserved for client compatibility, but there is no separate /atom route.

The token IS the credential — it carries no Bearer header, and anyone with the URL can read the feed. Treat it like a password. Find or rotate it from the dashboard under Feeds.

Subscribe from Slack, RSS readers, or automation tools. Most readers handle Atom transparently.

Treat the URL like an API key. The token appears in HTTP referer headers, web-server logs, and any system that processes the URL. Rotate it from the dashboard if it’s exposed (paste into the wrong chat, leaked in a screenshot, etc.).

You can generate a read-only permalink for your incident feed. This is useful for:

  • Sharing with team members who don’t have an account
  • Embedding in internal status dashboards
  • Providing a human-readable fallback alongside webhooks

Manage shareable feed URLs from the dashboard.

A separate feed for platform announcements (maintenance, new features, policy changes) is available at:

https://api.uptimemonitoring.com/feed.xml

The body is Atom XML and is open (no auth). Subscribe from your feed reader of choice.