shipapis
StarSubmit an APISubmit API

Currents vs WHO Global Health Observatory API

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

APICurrentsHEALTHY93WHO Global Health Observatory APIHEALTHY80
Uptime · 30d
Uptime · 90d100%88.2%
Uptime · 30d100%81.7%
P50 · ms586872
P95 · ms11652320
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs WHO Global Health Observatory API: common questions

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

On our scheduled checks, Currents leads on measured uptime — Currents at 100% versus WHO Global Health Observatory API at 88.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, Currents or WHO Global Health Observatory API?

Currents has the lower median latency in our checks — Currents responds in 586 ms versus WHO Global Health Observatory API at 872 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 Currents and WHO Global Health Observatory API need an API key?

WHO Global Health Observatory API needs no key, while Currents requires a free API key. If you want to start calling without signup, reach for WHO Global Health Observatory API first.

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

Neither sends browser-friendly CORS headers reliably, so call Currents and WHO Global Health Observatory API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Currents and WHO Global Health Observatory API free for commercial use?

Currents 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.