Find Public APIsA building block for your next idea.
Build a barcode product lookup showing available ingredients, source links, and missing-data states.
Know before you build
Public reads require an identifying User-Agent; writes need authentication. Follow endpoint rate limits, attribution, and share-alike conditions. Data is community-contributed and may be incomplete. Use staging for testing.
Check current provider documentation ↗Your first request
Start with this documented example. Replace credential placeholders with your own test credentials. Browser execution depends on the provider’s CORS policy.
curl --request GET 'https://world.openfoodfacts.org/api/v3.6/product/3274080005003.json'This provider requests an identifying User-Agent in server integrations. Browsers control that header; the browser playground omits it. Consult provider requirements before using a browser-only integration in production.
Practical questions
What can I build with Open Food Facts?+
Build a barcode product lookup showing available ingredients, source links, and missing-data states.
Does Open Food Facts need authentication?+
The reviewed example is listed as “No key”. Public reads require an identifying User-Agent; writes need authentication. Follow endpoint rate limits, attribution, and share-alike conditions. Data is community-contributed and may be incomplete. Use staging for testing.
Can I call Open Food Facts from a browser?+
Browser access depends on the provider’s CORS policy for your origin, method, and headers. The playground makes a direct request and cannot bypass those restrictions.
Sources & confidence
Provider documentation was reviewed on 16 September 2026. This is not a live availability test or an endorsement.
Source catalogs can become outdated. Read our review and attribution policy. Plain-text guide ↗