Open Food Facts · Authentication Profile

Open Food Facts Authentication

Authentication

Open Food Facts secures its APIs with apiKey, http, and oauth2 across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the password flow(s).

FoodNutritionOpen DataProduct DataBarcodesTaxonomyPricesSearchFood and Beverage

Methods: apiKey, http, oauth2 Schemes: 4 OAuth flows: password API key in: cookie, header

Security Schemes

cookieAuth apiKey

· in: cookie (session)

userAgentAuth apiKey

· in: header (User-Agent)

OAuth2PasswordBearer oauth2

· flows: password

CustomAuthentication http

scheme: bearer

Source

Authentication Profile

generated: '2026-09-17'
method: derived
source: openapi/open-food-facts-api-v2-openapi.yml, openapi/open-food-facts-api-v3-openapi.yml,
  openapi/open-food-facts-folksonomy-openapi.json, openapi/open-food-facts-open-prices-openapi.yml
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - cookie
  - header
  oauth2_flows:
  - password
schemes:
- name: cookieAuth
  type: apiKey
  in: cookie
  parameter: session
  description: |-
    Session cookie containing user ID, username, and session token.
    The value is structured as: user_id&username&user_session&session_token
    e.g. "user_id&exampleuser&user_session&abcdefghijklmnopqrstuvwxyz123456789ABCDEFGHIJKLM".
    The session token is obtained after successful login via the `/cgi/session.pl` endpoint.
  sources:
  - openapi/open-food-facts-api-v2-openapi.yml
  - openapi/open-food-facts-api-v3-openapi.yml
- name: userAgentAuth
  type: apiKey
  in: header
  parameter: User-Agent
  description: 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 source of problematic
    API queries, we may have to block them. User-Agent header in the format 'app_name/app_version
    (URL or contact info)'
  sources:
  - openapi/open-food-facts-api-v2-openapi.yml
  - openapi/open-food-facts-api-v3-openapi.yml
- name: OAuth2PasswordBearer
  type: oauth2
  flows:
  - flow: password
    tokenUrl: auth
    scopes: 0
  sources:
  - openapi/open-food-facts-folksonomy-openapi.json
- name: CustomAuthentication
  type: http
  scheme: bearer
  sources:
  - openapi/open-food-facts-open-prices-openapi.yml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/open-food-facts-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.