shipapis
StarSubmit an APISubmit API

University of Oslo vs WHO Global Health Observatory API

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

APIUniversity of OsloNEW—WHO Global Health Observatory APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

University of Oslo vs WHO Global Health Observatory API: common questions

Which is more reliable, University of Oslo or WHO Global Health Observatory API?

On our scheduled checks, WHO Global Health Observatory API leads on measured uptime — University of Oslo at —% versus WHO Global Health Observatory API at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do University of Oslo and WHO Global Health Observatory API need an API key?

Neither needs a paid key — University of Oslo is callable with no signup, and WHO Global Health Observatory API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call University of Oslo and WHO Global Health Observatory API from the browser?

Only University of Oslo is browser-friendly — it returns CORS headers over HTTPS. WHO Global Health Observatory API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are University of Oslo and WHO Global Health Observatory API free for commercial use?

University of Oslo has unclear commercial terms, and WHO Global Health Observatory API 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.