Open Food Facts API Rate Limits in Production Apps
Published June 14, 2026
Teams start with Open Food Facts because it is free and open. Then launch day arrives and search slows to a crawl or returns HTTP 429. This article explains Open Food Facts API rate limits in production apps, why typeahead search breaks, and when a commercial food API like Calorie API is the right move.
How Open Food Facts Rate Limiting Works
Open Food Facts is a volunteer-powered database. Public API access is shared by researchers, hobby apps, and commercial products. Heavy or bursty traffic triggers:
| Symptom | Likely cause |
|---|---|
| HTTP 429 Too Many Requests | Shared quota exceeded |
| Slow search responses | Server-side throttling |
| Blocked autocomplete | Aggressive crawl protection |
| Intermittent timeouts | Peak global usage |
Search-as-you-type sends one request per keystroke without debouncing. That pattern alone can exhaust polite-use limits during a marketing push.
Production Patterns That Break OFF
- No debounce on mobile search (300 ms minimum)
- No caching of popular foods
- Barcode storm on gym launch day
- Serverless fan-out (each user × each keystroke)
- Missing User-Agent identification (OFF asks for descriptive agents)
Mitigations While Staying on OFF
| Fix | Impact |
|---|---|
| Debounce 300 to 500 ms | Cuts calls 80%+ |
| Cache Redis results 10 min | Removes duplicate queries |
| Batch barcode lookups | One call per scan, not per screen |
| Self-host OFF dump | Ops heavy, data stale without ETL |
| Contact OFF for commercial use | Uncertain SLA |
Even with fixes, OFF offers no commercial SLA for revenue apps.
Open Food Facts vs Calorie API for Production
| Factor | Open Food Facts | Calorie API |
|---|---|---|
| Cost | Free | Free tier + paid plans |
| SLA | None | Production support on paid tiers |
| Barcode | Yes (crowdsourced) | Yes (curated + verified filter) |
| Search suggest | Limited / throttled | Built for app UX |
| Data quality | Variable crowdsourcing | Verified foods filter |
| Commercial license | Gray area for paid apps | Clear Plus licensing |
For a revenue-generating calorie tracker, predictable limits beat free but throttled.
Migration Path OFF → Calorie API
Step 1: Proxy both vendors temporarily
Your backend route tries Calorie API first, falls back to OFF during transition.
Step 2: Map response shapes
Both return name and macros. Normalize to your internal FoodItem model:
type FoodItem = {
id: string;
source: 'calorie_api' | 'off';
name: string;
caloriesPer100g: number;
proteinG: number;
carbsG: number;
fatG: number;
};
Step 3: Swap mobile clients to proxy only
Clients never call OFF or Calorie API directly. Change upstream in env.
Step 4: Monitor quota
Calorie API dashboard shows monthly usage. Upgrade before Black Friday.
Code Example: Calorie API Search (Replacement)
curl "https://api.calorieapi.com/api/v1/search/foods?q=skyr&limit=5&verified_only=true" \
-H "X-API-Key: YOUR_KEY"
Proxy through Next.js or Firebase.
When OFF Still Makes Sense
- Academic research prototypes
- Non-commercial open source tools
- Internal dashboards with low traffic
- Products with ops team to self-host dumps
When to Choose Calorie API Instead
- App Store apps with paying users
- Barcode + search UX with sub-second suggest
- Need verified macro data
- Want free tier without credit card then scale to Plus
Related Comparisons
Frequently Asked Questions
Does Open Food Facts have API rate limits?
Yes. The public Open Food Facts API applies usage limits and may return HTTP 429 when traffic is too high. Production apps need debouncing, caching, or a commercial alternative.
Why does Open Food Facts block search as you type?
Autocomplete sends many requests per second across shared infrastructure. OFF may throttle or slow responses to protect servers.
What is the best Open Food Facts alternative for production apps?
Calorie API offers search, suggest, barcode lookup, verified foods, transparent pricing, and a free tier designed for commercial calorie tracking apps.
Can I use Open Food Facts in a paid App Store app?
Open Food Facts is open data but lacks a commercial SLA. Paid apps typically migrate to licensed food APIs like Calorie API for predictable limits and support.
How do I migrate from Open Food Facts to Calorie API?
Build a backend proxy with a normalized FoodItem model, point mobile clients at your proxy, switch upstream to Calorie API, and monitor quota in the Calorie API dashboard.