FoodData Central vs Open Food Facts API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limit10 req/window · 9 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

FoodData Central vs Open Food Facts API: common questions

Which is more reliable, FoodData Central or Open Food Facts API?

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

Open Food Facts API needs no key, while FoodData Central requires a free API key. If you want to start calling without signup, reach for Open Food Facts API first.

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

Yes — both FoodData Central and Open Food Facts API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are FoodData Central and Open Food Facts API free for commercial use?

FoodData Central 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.