shipapis
StarSubmit an APISubmit API

Open Food Facts API vs Squiggle

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

APIOpen Food Facts APINEW—SquiggleNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Food Facts API vs Squiggle: common questions

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

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

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

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

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

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

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