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