OWASP API Security Project vs WHO Global Health Observatory API

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

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

OWASP API Security Project vs WHO Global Health Observatory API: common questions

Which is more reliable, OWASP API Security Project or WHO Global Health Observatory API?

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

Neither needs a paid key — OWASP API Security Project 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 OWASP API Security Project and WHO Global Health Observatory API from the browser?

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

OWASP API Security Project 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.