shipapis
StarSubmit an APISubmit API

Open Food Facts vs RecipeAPI

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

APIOpen Food FactsDYING29RecipeAPIDEAD0
Uptime · 30d
Uptime · 90d39.2%0.0%
Uptime · 30d33.3%0.0%
P50 · ms1556—
P95 · ms2836—
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Food Facts vs RecipeAPI: common questions

Which is more reliable, Open Food Facts or RecipeAPI?

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

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

Can I call Open Food Facts and RecipeAPI from the browser?

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

Are Open Food Facts and RecipeAPI free for commercial use?

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