shipapis
StarSubmit an APISubmit API

WHO Global Health Observatory API vs Zenodo

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

APIWHO Global Health Observatory APINEW—ZenodoNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

WHO Global Health Observatory API vs Zenodo: common questions

Which is more reliable, WHO Global Health Observatory API or Zenodo?

On our scheduled checks, Zenodo leads on measured uptime — WHO Global Health Observatory API at —% versus Zenodo 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 WHO Global Health Observatory API and Zenodo need an API key?

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

Can I call WHO Global Health Observatory API and Zenodo from the browser?

Only Zenodo 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 WHO Global Health Observatory API and Zenodo free for commercial use?

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