Status API

CORS

GET responses from /api/status, /api/v2/status, /api/status/stream, /api/v2/status/stream, /api/status/uptime, /api/v2/status/uptime, /api/incidents, and /api/v2/incidents include Access-Control-Allow-Origin: * so browser-based dashboards can fetch them without a same-origin proxy.

Mobile and in-app integration

Native Android, iOS, and hybrid shells can treat the status host as a read-only JSON API (no LicenseChain session required).

val client = OkHttpClient()
val req = Request.Builder()
  .url("https://status.licensechain.app/api/status")
  .get()
  .build()
client.newCall(req).execute().use { resp ->
  val body = resp.body?.string() ?: ""
  // Parse JSON: status, services, metrics, lastUpdated
}

let url = URL(string: "https://status.licensechain.app/api/status")!
URLSession.shared.dataTask(with: url) { data, _, _ in
  guard let data = data else { return }
  // Decode JSON: status, services, metrics, lastUpdated
}.resume()

Use HTTPS, respect battery (avoid sub-second polling), and surface lastUpdated or checkedAt from payloads so users know data freshness.

Service summary

GET /api/status

Returns aggregated service rows with human-oriented labels and formatted uptime strings.

Response (200):

• status — operational | degraded
• services[] — name, status, description, lastChecked, responseTime, uptime, category, and optional regions[] when multi-region monitoring is configured (code, status, responseTime?, checkedAt ISO). Health-check URLs are never included.
• metrics — operational, total, avgResponseTime, uptime
• lastUpdated — ISO timestamp

Multi-region monitoring

When multi-region probes are configured, the public API exposes region codes and rolled-up status only — never probe URLs.

GET /api/status/stream

Server-Sent Events (text/event-stream): repeated JSON snapshots with the same shape as GET /api/status. Default push interval is 15s; optional query interval (seconds, clamped 5–60). Browsers and mobile WebViews can subscribe with EventSource when same-origin or CORS allows.

GET /api/status/uptime

Query parameters:

• days — lookback window (default 30, max 90).
• service — optional; filter to one service name.
• region — optional; filter to one probe region code. Requires service when set.

Response: { success, service, region, days, points[] } where each point has bucket (date), uptime (0–100), and checks.

API v2 (stable schema for integrations)

Prefer these paths for new clients; v1 remains supported for existing embeds.

GET /api/v2/status

• api.version — "2.0"
• generatedAt — ISO-8601
• overall.status — operational | degraded
• metrics — operational, total, avgResponseTimeMs, avgUptimePercent
• services[] — id, name, status, description, lastCheckedAt (ISO), responseTimeMs, uptimePercent, category, monitorRegions[] (code only), optional regions[] (code, status, responseTimeMs, checkedAt ISO). Health-check URLs are never included.

GET /api/v2/status/stream

SSE with the same JSON body as GET /api/v2/status; query interval (seconds, 5–60, default 15).

GET /api/v2/status/uptime

Same query semantics as v1, with envelope: api, generatedAt, success, service, region, days, points.

GET /api/v2/incidents

Same query params as v1 (limit, q, status, service). Response includes api, generatedAt, success, and incidents[] with ISO date fields (startsAt, endsAt, createdAt, updatedAt, resolvedAt — nullable where applicable). Each incident may include timeline: an array of { at, fromStatus?, toStatus?, message? } with public messages and status transitions only.

GET /api/v2/status/customization

Public branding payload: brandName, logoUrl, supportUrl, whiteLabelEnabled, publicSiteUrl, themeCssVars.

GET /api/v2/enterprise/features

High-level enterprise flags and counters for status-page capabilities.

RSS feed

GET /api/status/rss

RSS/Atom feed of recent incidents (linked via <link rel="alternate"> on the status site).

Incidents

GET /api/incidents

Supports filters such as q, status, and service. Returns incident records for the status UI and external consumers. Payload matches v2 incident objects, including optional timeline (public workflow activity).

Outbound service-change webhook

When a monitored service changes status (for example operational → degraded), an optional outbound webhook can notify your endpoint. Example body:

{
  "source": "licensechain-status",
  "event": "service_status_changed",
  "service": {
    "name": "API Service",
    "previousStatus": "operational",
    "newStatus": "degraded",
    "checkedAt": "2026-04-04T12:00:00.000Z"
  }
}