The public page

What GET /public/status/{slug} returns, unauthenticated, today.

The public page

curl https://api.up0.io/api/v1/public/status/<SLUG>

No authentication, no header, no token. A page created with is_public: true (the default, see Pages and components) answers on this URL for anyone. A page that does not exist, or exists with is_public: false, answers 404.

This is a JSON response, not an HTML page

Walking this live is exactly what the screenshot below shows: a browser navigated straight at the URL renders the platform's own JSON viewer, because that is genuinely what is served. There is no rendered status page today. See the note on the Status pages index.

A browser navigated directly to the public status page endpoint, showing the raw JSON response: name, slug, description, overall_status and one component.

{
  "name": "1648 example",
  "slug": "1648-example",
  "description": "docs walk status page",
  "branding": {},
  "overall_status": "operational",
  "components": [
    {
      "name": "1648 example http",
      "description": "bound to the 1648 example http monitor",
      "status": "operational",
      "updated_at": "2026-09-16T13:05:09.811621+00:00"
    }
  ]
}

branding carries logo_url, primary_color and custom_css when set on the page, empty otherwise. Components are returned in sort_order.

Incidents and subscribers

curl https://api.up0.io/api/v1/public/status/<SLUG>/incidents

Returns incidents linked to the page (also unauthenticated, also 404 on a private or missing page). Linking an incident to a page is a separate, organization-scoped call (POST /api/v1/me/status-pages/{id}/incidents), not covered here.

A visitor can subscribe to email updates for a page:

curl -X POST https://api.up0.io/api/v1/public/status/<SLUG>/subscribe \
  -H "Content-Type: application/json" \
  -d '{ "email": "customer@example.com" }'

This is double opt-in: the address is not active until the visitor follows a confirmation link mailed to them. That mail is sent through the same SMTP configuration every other transactional email on the platform uses; on a stack with no SMTP configured (most local and kind clusters), the subscription is accepted but the confirmation email is never sent, and the address can never be confirmed.

On this page