shipapis
StarSubmit an APISubmit API

Foodish vs Open Food Facts API

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

APIFoodishDYING53Open Food Facts APIHEALTHY78
Uptime · 30d
Uptime · 90d27.5%94.1%
Uptime · 30d11.7%95.0%
P50 · ms2501401
P95 · ms7604168
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Unverified
Free tierFree — no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs Open Food Facts API: common questions

Which is more reliable, Foodish or Open Food Facts API?

On our scheduled checks, Open Food Facts API leads on measured uptime — Foodish at 27.5% versus Open Food Facts API at 94.1% 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, Foodish or Open Food Facts API?

Foodish has the lower median latency in our checks — Foodish responds in 250 ms versus Open Food Facts API at 1401 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 Foodish and Open Food Facts API need an API key?

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

Can I call Foodish and Open Food Facts API from the browser?

Only Open Food Facts API is browser-friendly — it returns CORS headers over HTTPS. Foodish needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Foodish and Open Food Facts API free for commercial use?

Foodish has unclear commercial terms, and Open Food Facts 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.