shipapis
StarSubmit an APISubmit API

LCBO vs openFDA API

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

APILCBOHEALTHY98openFDA APIHEALTHY88
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms207806
P95 · ms4291868
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?

Both are neck-and-neck — LCBO and openFDA API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, LCBO or openFDA API?

LCBO has the lower median latency in our checks — LCBO responds in 207 ms versus openFDA API at 806 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 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.