shipapis
StarSubmit an APISubmit API

WHO Global Health Observatory API vs REST Countries

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

APIWHO Global Health Observatory APIUNMONITORED—REST CountriesHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedMPL-2.0
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone published
In directory since2026-07-052026-05-02
operationalpartialdownno data

WHO Global Health Observatory API vs REST Countries: common questions

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

Only REST Countries is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do WHO Global Health Observatory API and REST Countries need an API key?

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

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

Only REST Countries 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 REST Countries free for commercial use?

WHO Global Health Observatory API has unclear commercial terms, and REST Countries allows commercial use on its free tier. 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.