shipapis
StarSubmit an APISubmit API

LCBO vs openFDA API

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

APILCBONEW—openFDA APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs openFDA API: common questions

Which is more reliable, LCBO or openFDA API?

On our scheduled checks, openFDA API leads on measured uptime — LCBO at —% versus openFDA 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 LCBO and openFDA API need an API key?

Neither needs a paid key — LCBO is callable with no signup, and openFDA API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call LCBO and openFDA API from the browser?

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

Are LCBO and openFDA API free for commercial use?

LCBO has unclear commercial terms, and openFDA 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.