Open Food Facts Python API Docs | dltHub

Build a Open Food Facts-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Open Food Facts is an open database of food products that provides an API for reading product information and contributing data to the database. The REST API base URL is https://world.openfoodfacts.org and write operations require credentials in the request body.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Open Food Facts data in under 10 minutes.


What data can I load from Open Food Facts?

Here are some of the endpoints you can load from Open Food Facts:

ResourceEndpointMethodData selectorDescription
product/api/v2/product/{code}GETGet product details by barcode
search/api/v2/searchGETproductsSearch products with filters and pagination
attribute_groups/api/v2/attribute_groupsGETList product attribute groups
preferences/api/v2/preferencesGETGet preferences weights
taxonomy_suggestions/api/v3/taxonomy_suggestionsGETGet taxonomy suggestions
external_sources/api/v3/external_sourcesGETList external knowledge panel sources

How do I authenticate with the Open Food Facts API?

Authentication is only required for write operations; credentials (user_id and password) are sent as body parameters in the POST request.

1. Get your credentials

Open Food Facts does not use traditional API keys. For write operations (such as adding or editing products), you must use your Open Food Facts account credentials (username and password). 1. Create an account on the official Open Food Facts website or app. 2. Use your unique 'user_id' (which is your username, not your email) and your account password. 3. For secure sessions, you can use the '/cgi/session.pl' endpoint to obtain a session cookie to use in subsequent requests. Alternatively, you can pass 'user_id' and 'password' directly in the body of POST requests. Note: You should also include a descriptive 'User-Agent' header in all requests (format: 'AppName/Version (ContactEmail)') to identify your integration.

2. Add them to .dlt/secrets.toml

[sources.open_food_facts_source] user_id = "your_username" password = "your_password" user_agent = "my_app_name/1.0 (contact@example.com)"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Open Food Facts API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python open_food_facts_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline open_food_facts_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset open_food_facts_data The duckdb destination used duckdb:/open_food_facts.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads '/cgi/session.pl' and '/api/v2/search' from the Open Food Facts API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def open_food_facts_source(user_id_password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://world.openfoodfacts.org", "auth": {"type": "bearer", "token": user_id_password}, }, "resources": [ {"name": "search", "endpoint": {"path": "api/v2/search", "data_selector": "products"}}, {"name": "product", "endpoint": {"path": "api/v2/product/{code}", "data_selector": "product"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="open_food_facts_pipeline", destination="duckdb", dataset_name="open_food_facts_data", ) load_info = pipeline.run(open_food_facts_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("open_food_facts_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM open_food_facts_data.search LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("open_food_facts_pipeline").dataset() data.search.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Open Food Facts data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Open Food Facts?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines