Going further

Status API

Fetch uptime, incidents and scheduled maintenance programmatically — no key needed.

Service status can be fetched programmatically from https://status.danskadresseapi.dk/api/v2/. The format follows Atlassian Statuspage v2 — the same one most monitoring tools (Datadog, Grafana, PagerDuty, Better Stack and others) already understand.

No API key. The status API is public and does not count towards your quota.

Quick start

Bash

curl "https://status.danskadresseapi.dk/api/v2/status.json"

JSON

{
  "page": { "name": "…", "url": "https://status.danskadresseapi.dk", "time_zone": "Europe/Copenhagen", "language": "en" },
  "status": { "indicator": "none", "description": "…" }
}

Endpoints

Path	Contents
`/api/v2/status.json`	Overall indicator
`/api/v2/summary.json`	Everything at once: components, open incidents, active maintenance
`/api/v2/components.json`	Each component with status and uptime (90 days)
`/api/v2/incidents.json`	Recent incidents (including resolved)
`/api/v2/incidents/unresolved.json`	Open incidents only
`/api/v2/scheduled-maintenances.json`	All scheduled maintenance
`/api/v2/scheduled-maintenances/upcoming.json`	Upcoming maintenance
`/api/v2/scheduled-maintenances/active.json`	Maintenance in progress

Values

status.indicator: none · minor · major · critical · maintenance

Component status: operational · degraded_performance · partial_outage · major_outage · under_maintenance

Language

Add ?lang=en for English titles and updates. Without the parameter you get the page's default language.

Caching and limits

Responses are cached for 30 seconds (Cache-Control: public, max-age=30) — polling faster does not give fresher data.
ETag is supported: send If-None-Match and you get 304 with no body when nothing changed.
At most 300 requests per minute per IP. Polling every 30–60 seconds is plenty.
CORS is open (Access-Control-Allow-Origin: *), so it can be called directly from a browser.

Do not use the status API as a health check for your own integration. It tells you what
we know about the service — not whether your calls succeed. Measure your own responses for that.