barcode JSON API v2

The barcode JSON API v2 is the live read pattern behind the Open Food Facts database: you append an EAN/UPC barcode to /api/v2/product/{barcode}.json and receive that single product's record as JSON. The catalog it serves holds 4,697,746 indexed products with Nutri-Score and Green-Score, and is filterable by category. Open Food Facts lists 'JSON (API v2)' among its data formats and marks the feed's update frequency as realtime, so a record edited today is what the endpoint returns today. The same project also publishes nightly exports, which makes the API the freshest access path and the exports the cheapest bulk path; both are covered by the project's open licence.

Without a per-barcode endpoint you fetch whole files to answer one product question. A price or shelf-audit workflow that scans a handful of SKUs would otherwise download and re-parse a large catalog on every run. The v2 pattern keeps lookups one request per item and returns structured JSON rather than a page to scrape. It matters most when freshness does: because Open Food Facts updates in realtime, an app that checks a barcode at scan time sees contributions made minutes earlier, while an export-based pipeline shows yesterday's snapshot. Buyers should still confirm the volume profile - polling millions of barcodes one call at a time is slower than pulling the nightly file once.

1. Confirm the URL shape: Open Food Facts documents product JSON at /api/v2/product/{barcode}.json, so any source claiming v2 compatibility should expose the same per-barcode path.

1. Check index depth against your need: the endpoint covers 4,697,746 indexed products - if your category coverage matters, verify records exist before building on it.

1. Check enrichment fields, not just a payload: the Open Food Facts API carries Nutri-Score and Green-Score and supports category filtering.

1. Check update cadence: Open Food Facts lists its data_formats as including 'JSON (API v2)' and its update_frequency as realtime, paired with nightly full exports.

These entries cover the surrounding access patterns:

• barcode-product-sku
• nightly-full-export
• commercial delivery terms-open-database-license