Public incident history for a status page
GET/api/v1/status-pages/:org/:slug/incidents
The customer-facing incidents published on this page (spec 2026-08-19-08). Without active, returns the page's history window; with active=true, only the incidents that are still open — the same set the full page view embeds as activeIncidents[].
Same visibility gate as the full page view: a disabled or non-public page returns 404, identical to a page that doesn't exist. Same caching rule too — Cache-Control: public, max-age=60, stale-while-revalidate=30 for a public page, private, no-store for a password or private one (unlocked or not), since this payload quotes incident titles and update bodies verbatim. No authentication required.
Every field is operator-authored or templated from the page's own public resource names. Probe output, error strings and internal hostnames are structurally unable to reach this payload.
Request
Responses
- 200
- 401
- 404
The page's public incidents
The status page is password protected and the request carried no valid unlock cookie. The error code is STATUS_PAGE_LOCKED, deliberately distinct from a generic UNAUTHORIZED: it means "unlock me", not "log in" — public status pages have no accounts. Obtain the cookie from POST /api/v1/status-pages/{org}/{slug}/unlock and replay it.
Resource not found