Registrum API vs Umeå Open Data

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%89.2%
Uptime · 30d100%81.7%
P50 · ms2461445
P95 · ms15534863
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedVaries by dataset (municipal open data; see portal)
Free tierFree tier — API key requiredFree — open data portal, no key
Rate limitUnpublished1000 req/window · 999 remaining · resets 2026-07-09 00:00:00+00:00
In directory since2026-07-052026-07-05
operationalpartialdownno data

Registrum API vs Umeå Open Data: common questions

Which is more reliable, Registrum API or Umeå Open Data?

On our scheduled checks, Registrum API leads on measured uptime — Registrum API at 100% versus Umeå Open Data at 89.2% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Registrum API or Umeå Open Data?

Registrum API has the lower median latency in our checks — Registrum API responds in 246 ms versus Umeå Open Data at 1445 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Registrum API and Umeå Open Data need an API key?

Umeå Open Data needs no key, while Registrum API requires a free API key. If you want to start calling without signup, reach for Umeå Open Data first.

Can I call Registrum API and Umeå Open Data from the browser?

Only Umeå Open Data is browser-friendly — it returns CORS headers over HTTPS. Registrum API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Registrum API and Umeå Open Data free for commercial use?

Registrum API has unclear commercial terms, and Umeå Open Data has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.