How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Open Food Facts Products API

Endpoints for managing product data and information.

Open Food Facts Products API is one of 46 APIs that Open Food Facts publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Product. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a changelog.

This API exposes 12 operations across 11 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 5 base URLs: https://world.openfoodfacts.net, https://world.openfoodfacts.org, http://localhost:8080, https://api.folksonomy.openfoodfacts.org, http://localhost:8000.

12 operations 11 paths 11 schemas 7 GET3 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://world.openfoodfacts.net
Authentication
API Key, API Key, OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 4

Open Food Facts Products API declares 4 security schemes for authenticating requests. An API key is passed in the cookie as session (cookieAuth). An API key is passed in the header as User-Agent (userAgentAuth). It supports OAuth 2.0 (OAuth2PasswordBearer) using the password flow. It accepts HTTP bearer tokens (CustomAuthentication).

  • cookieAuth — Session cookie containing user ID, username, and session token. The value is structured as: userid&username&usersession&sessiontoken e.g. "userid&exampleuser&u…
  • userAgentAuth — Identification using the User-Agent header. This is recommended in all requests so that we can contact you if there are issues. If we cannot identify the sourc…

Paths & Operations 12

Across 11 paths, the API surfaces 12 operations — 7 GET, 3 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Products 12

Endpoints for managing product data and information.

GET
/api/v2/product/{code}
Get Product Details
get-product-by-code 11 params → 200302404
POST
/cgi/product_jqm2.pl
Edit Product
post-cgi-product_jqm2.pl body → 200
GET
/api/v3/product/{code}
Get Product Data
get-api-v3-product-code 11 params → 200302404
PATCH
/api/v3/product/{code}
Create or Update Product
patch-api-v3-product-code 1 param body → 200
POST
/api/v3/product_revert
Revert Product to Previous Revision
post-api-v3-product_revert body → 200
GET
/products/stats
Product Stats
product_stats_products_stats_get 3 params → 200422
GET
/products
Product List
product_list_products_get 3 params → 200422
GET
/api/v1/products
Products list
products_list 19 params → 200
GET
/api/v1/products/{id}
Products retrieve
products_retrieve 1 param → 200
GET
/api/v1/products/code/{code}
Products code retrieve
products_code_retrieve 1 param → 200
PATCH
/api/v1/products/code/{code}/off-update
Products code off update partial update
products_code_off_update_partial_update 1 param body → 200
PATCH
/api/v1/products/code/{code}/off-upload-image
Products code off upload image partial update
products_code_off_upload_image_partial_update 1 param body → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ProductFull (26 properties), PatchedProductFull (26 properties), PaginatedProductFullList (5 properties), ProductStats (4 properties). Each schema is shown below with its type and property counts.

Product-Knowledge-Panels
object
Knowledge panels for a product
1 property
ProductList
object
3 properties 3 required
ProductStats
object
4 properties 4 required
ValidationError
object
3 properties 3 required
HTTPValidationError
object
1 property
PaginatedProductFullList
object
5 properties 5 required
NullEnum
PatchedProductFull
object
26 properties
SourceEnum
string
off - off obf - obf opff - opff opf - opf
BlankEnum
ProductFull
object
26 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

open-food-facts-products-api-openapi.yml Raw ↑

Other APIs Open Food Facts publishes across the network.

Open Food Facts Cgi API
Open Food Facts Product API
Open Food Facts Search API
Open Food Facts Taxonomy API
Open Food Facts Taxonomy Suggestions API
Open Food Facts Admin - Property Management API
Open Food Facts Admin - Value Management API
Open Food Facts Auth API
Open Food Facts Authentication API
Open Food Facts Autocomplete API
Open Food Facts Badges API
Open Food Facts Challenges API
Where this information came from

This is an independent, third-party profile of Open Food Facts Products API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.