shipapis
StarSubmit an APISubmit API

Fruityvice vs Open Food Facts API

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

APIFruityviceNEW—Open Food Facts APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fruityvice vs Open Food Facts API: common questions

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

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

Neither needs a paid key — Fruityvice 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 Fruityvice and Open Food Facts API from the browser?

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

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

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