shipapis
StarSubmit an APISubmit API

BotsArchive vs WHO Global Health Observatory API

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

APIBotsArchiveHEALTHY86WHO Global Health Observatory APIHEALTHY80
Uptime · 30d
Uptime · 90d97.1%88.2%
Uptime · 30d95.0%81.7%
P50 · ms790872
P95 · ms44482320
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

BotsArchive vs WHO Global Health Observatory API: common questions

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

On our scheduled checks, BotsArchive leads on measured uptime — BotsArchive at 97.1% 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, BotsArchive or WHO Global Health Observatory API?

BotsArchive has the lower median latency in our checks — BotsArchive responds in 790 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 BotsArchive and WHO Global Health Observatory API need an API key?

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

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

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