Skip to main content

​
Public Status API

The public status API provides read-only availability indicators, component health, and recent incident records for public Tuturuuu platform services. Requests support GET and HEAD methods. Unsupported HTTP methods return 405 Method Not Allowed, and unrecognised routes return an empty 404 Not Found.

​
Routes

​
Response Envelope

All endpoints return a structured JSON envelope:
  • status: Aggregate availability state: operational, under_maintenance, degraded_performance, partial_outage, major_outage, or unknown.
  • components: Allowlisted component objects containing id, status, and updated_at (coarse UTC ISO timestamp rounded down to the minute). /api/v1/status returns an empty array.
  • generated_at: UTC timestamp of the underlying data snapshot, or null when unavailable.
  • stale: true if snapshot freshness exceeds allowable limits or publisher status is offline.
  • fallback: true if data is served from a fallback snapshot.

​
Freshness and ‘unknown’ Semantics

Availability status adheres to strict fail-safe rules:
  • Stale or Fallback: If snapshot data is older than 2 minutes, if publisher availability is down, or if served from fallback, all component states and aggregate status force to 'unknown'.
  • Empty or Unusable Store: If status data is unreadable, missing, or corrupt, endpoints return 503 Service Unavailable with explicit unknown status and null timestamp:

​
Caching and ETag Behaviour

  • ETag and 304 Validation: Weak ETags (W/"...") are computed across the HTTP status code and full JSON body, including freshness flags (stale, fallback). Any transition to stale changes the ETag, guaranteeing that 304 Not Modified never revalidates aged or degraded health records.
  • Cache-Control: Stale, fallback, and error responses send Cache-Control: no-store. Fresh responses specify public, max-age=0, s-maxage=<ttl>, stale-while-revalidate=<swr>. There is no stale-if-error. Both lifetimes end inside the remaining freshness window.

​
Privacy and Scope

Owned component IDs come only from the trusted STATUS_OWNED_COMPONENT_IDS binding. The snapshot tier is ignored. An approved ID that is not owned still needs recorded consent, and never-public IDs are excluded. Only approved public services are exposed. Excluded, tenant-specific, or unrecognised component IDs return an empty 404 Not Found indistinguishable from non-existent resources. Response payloads contain only generic identifiers, states, and coarse timestamps.