API and feeds

JSON files

English names and texts under /en/api/v2/, German ones under /api/v2/. The status values are the same in both.

/en/api/v2/status.json

Overall status: one value for all systems

/en/api/v2/summary.json

Everything at once: overall status, systems, current incidents, active and scheduled maintenance

/en/api/v2/components.json

The systems with their status

/en/api/v2/incidents.json

Incidents of the last 90 days, including automatically detected ones

/en/api/v2/incidents/unresolved.json

Only incidents that are still open

/en/api/v2/scheduled-maintenances.json

Maintenance of the last 90 days and scheduled maintenance

/en/api/v2/scheduled-maintenances/upcoming.json

Only scheduled maintenance

/en/api/v2/scheduled-maintenances/active.json

Only maintenance in progress

Example

This is status.json right now:

curl https://status.appoint4u.com/en/api/v2/status.json

{
  "page": {
    "id": "appoint4u",
    "name": "appoint4u",
    "url": "https://status.appoint4u.com/en/",
    "time_zone": "Europe/Berlin",
    "updated_at": "2026-11-04T20:53:06Z"
  },
  "status": {
    "indicator": "none",
    "description": "All systems operational"
  }
}

Values

status.indicator

none, minor, major, critical, maintenance

components[].status

operational, degraded_performance, partial_outage, major_outage, under_maintenance

incidents[].status

investigating, identified, monitoring, resolved

incidents[].impact

none, minor, major, critical

scheduled_maintenances[].status

scheduled, in_progress, verifying, completed

In addition to the Statuspage API, every system carries an “appoint4u” object: monitoring (automatic = checked automatically, manual = status updated by our team), uptime_90_days (uptime in per cent since start_date, over at most 90 days; calculated from the automatic checks and the incidents our team reports; null without data), last_checked_at (systems checked automatically only: time of the last check result, as of when the file was built) and checks_without_result (true when the automatic checks have had no result for an hour). Incidents carry “appoint4u.automatic” (true = detected by the automatic checks) and “appoint4u.false_alarm” (true = classed as a false alarm by our team; does not count as downtime), maintenance “appoint4u.cancelled” and “appoint4u.ended_by” (team = completed by our team, window = not completed in time and therefore ended with its announced window, otherwise null).

Feeds

For feed readers and notifications, e.g. in Slack or Microsoft Teams:

• RSS feed (Deutsch) https://status.appoint4u.com/feed.rss
• Atom feed (Deutsch) https://status.appoint4u.com/feed.atom
• RSS feed (English) https://status.appoint4u.com/en/feed.rss
• Atom feed (English) https://status.appoint4u.com/en/feed.atom

Good to know

• The files are static and can be fetched from any website (CORS). There is no key and no sign-in.
• page.updated_at is when the files were built. Without a change, that happens about once an hour. If the value is more than two hours old, or the file cannot be fetched, the status is unknown – please do not show “operational” then.
• The automatic checks usually run every 5 to 15 minutes; GitHub starts the runs without fixed times. A system counts as disrupted only after two failed check runs in a row at least four minutes apart, and as operational again only after two successful ones; the level shown is the milder of the last two runs. A change usually takes 10 to 30 minutes to show here. Our team reports on all other systems.
• Only public addresses without personal data are checked: the home page, the sign-in page and the health check of appoint4u.com, and the health check of the demo (for information only, it changes no status).
• GitHub Pages caches responses for up to 10 minutes. Please poll at most once a minute.
• All texts (names, updates, descriptions) are plain text without HTML. Show them as text, never as HTML.
• Uptime: a major outage counts in full, a partial outage at 30% as downtime; degraded performance and scheduled maintenance do not count. The figures are not a commitment; only the contractual agreements apply.