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 Authentication API

Endpoints for user authentication and session management.

Open Food Facts Authentication 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 Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a changelog.

This API exposes 3 operations across 3 paths, and defines 4 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.

3 operations 3 paths 4 schemas 3 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
Resource Areas
1

Authentication & Security 3

Open Food Facts Authentication API declares 3 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.

  • 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 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Authentication 3

Endpoints for user authentication and session management.

POST
/cgi/session.pl
Login Session
get-cgi-session.pl body → 200401
POST
/auth
Authentication
authentication_auth_post body → 200422
POST
/auth_by_cookie
Authentication By Cookie
authentication_by_cookie_auth_by_cookie_post 1 param → 200422

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Body_authentication_auth_post (6 properties), ValidationError (3 properties), TokenResponse (2 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

TokenResponse
object
2 properties 2 required
ValidationError
object
3 properties 3 required
Body_authentication_auth_post
object
6 properties 2 required
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

open-food-facts-authentication-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 Autocomplete API
Open Food Facts Badges API
Open Food Facts Challenges API
Open Food Facts Document API
Where this information came from

This is an independent, third-party profile of Open Food Facts Authentication 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.