Supaboard Uptime is a headless monitoring engine you build into your own product. It checks your endpoints on the schedule you set, opens an incident after consecutive failures, and sends one notification per state change — over webhook, email, Slack or Telegram. Everything happens through a REST API; there is no dashboard.
curl -X POST https://uptime.supaboard.app/v1/monitors \
-H "X-RapidAPI-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://api.myapp.com/health", "interval_seconds": 60}'Intervals from 1 minute to 1 hour, with TTFB latency, custom request headers (stored encrypted) and 7 outcome classes — timeout, DNS, TLS and more.
An incident opens after N consecutive failures (you choose N) and resolves on the first success. Each state change triggers exactly one notification; outages shorter than 60 seconds are merged into a single "brief outage" message.
Every HTTPS monitor tracks its certificate and notifies you 30, 14 and 7 days before expiry. Monitor responses include ssl_expires_at and ssl_days_remaining. Included on all plans.
HMAC-signed webhooks, email, Slack incoming webhooks and Telegram. Each channel has a synchronous test call, so you can confirm delivery before you depend on it.
SSRF-guarded checker with DNS pinning; private and link-local targets are rejected. Your monitor headers are AES-256-GCM encrypted at rest.
OpenAPI 3.1 spec, ready-made Postman collection, one predictable error shape ({ error: { code, message } }) and plan limits enforced server-side.
POST /v1/monitors with a URL and an interval. Checks begin on the schedule you chose — nothing else to configure.
POST /v1/channels with a webhook URL, email address, Slack hook or Telegram chat ID, then confirm it with a synchronous test call.
Query check history, uptime percentages and incidents over the API and render them in your own status page or admin panel, under your own brand.
Subscribe through RapidAPI — no separate account needed.
Checks run at the interval you configure — from 1 minute on ULTRA and MEGA up to 60 minutes on BASIC. An incident is confirmed after N consecutive failures (default 2, configurable per monitor), and the notification is dispatched as soon as the incident opens.
Yes — that is the point. History, stats and incidents are all API-accessible; render them however you like.
Yes, on every plan. HTTPS monitors track certificate expiry and alert you 30, 14 and 7 days before it lapses; responses include ssl_expires_at and ssl_days_remaining. Keyword checks and multi-region verification are on the roadmap.