Status
How status.selyf.com, the health endpoint, and the incident feed relate to each other -- not a copy of the status page itself.
Two independent data sources, one page
The public status page at status.selyf.com is a standalone deployment, independent of the main API, so it stays reachable even during an incident affecting the API itself. It builds its view from two API endpoints, both public and documented in the API Reference: GET /health for live component reachability, and GET /api/status/incidents for the incident and maintenance history.
GET /health
A liveness/readiness probe reporting database, Gmail-integration, and AI-provider reachability at the moment it is called -- what the status page’s "operational / degraded / down" indicators reflect right now. It carries no history; it only ever reports the current instant.
GET /api/status/incidents
A public, read-only feed of past and current incidents and scheduled maintenance windows, each with a kind, state, title, message, and the components it affects. This is what backs the status page’s incident timeline, separate from the live reachability check above.
The API’s own root page
api.selyf.com's own root path renders a human-facing page showing this same live status, computed server-side from the exact same underlying checks GET /health uses -- so it can never drift out of sync with what /health itself reports at the same moment.
For live status, visit status.selyf.com directly. For the exact request/response shape of both endpoints above, see API Reference.