Monitoring data where you need it

Show service status on your website, pull alerts and incidents into your systems and receive events by webhook. No access to internal monitor details.

Public status API

Anonymous methods return only what you allowed to show: products, their state and uptime. It is enabled separately for the business, product and resource.

  • GET/PublicStatus/Products
  • GET/PublicStatus/ProductStatus
  • GET/PublicStatus/ProductUptime
  • GET/PublicStatus/StatusPage
  • GET/PublicStatus/StatusPageHistory
  • GET/PublicStatus/UptimeHistory
  • GET/PublicStatus/Rss
  • POST/PublicStatus/Subscribe

Key-based read API

Monitors, alerts and incidents for your reports and internal dashboards. The key is sent in a header, shown once and can be limited to an organization.

  • GET/v1/Monitors
  • GET/v1/Alerts
  • GET/v1/Incidents
  • HEADERAPI-KEY
API documentation

Published by choice, private by default

The public API never returns URLs, headers, check conditions, IP addresses or traces. The read API is read-only: you cannot change monitors through it.

  • Caching with ETag
  • Rate limiting for anonymous requests
  • Allowlist of CORS origins
  • Periods of 24 hours, 7, 30 and 90 days

Events and import

  • Signed webhooks

    The “webhook” notification channel sends events to your URL with an HMAC signature so you can verify the sender.

  • Status page subscriptions

    Customers and your systems subscribe to updates by email, webhook or RSS.

  • Check import

    Monitors are created from OpenAPI 3, Swagger 2 and Postman v2.1 collections.

  • Status badge

    A script of about 2 KB shows the status on your website without any frameworks.

Show service status on your website

Full descriptions of methods and models are in the interactive documentation. A read API key is created in the business settings.