Pepesto Python API Docs | dltHub

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

Last updated:

Pepesto is a grocery API that provides recipe parsing, ingredient matching to supermarket SKUs, and checkout session management for grocery applications and agents. The REST API base URL is https://s.pepesto.com/api/ and all requests require a Bearer token in the Authorization header, except for the /link endpoint used to obtain the key..

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 Pepesto data in under 10 minutes.


What data can I load from Pepesto?

Here are some of the endpoints you can load from Pepesto:

ResourceEndpointMethodData selectorDescription
linkapi/linkPOSTMint an API key.
creditsapi/creditsPOSTCheck credit balance.
oneshotapi/oneshotPOSTParse recipe and create checkout cart.
parseapi/parsePOSTParse recipe URL/text into structured data.
suggestapi/suggestPOSTSearch recipe knowledge graph.
productsapi/productsPOSTMap ingredients to ranked supermarket products.
sessionapi/sessionPOSTCreate a checkout session.
checkoutapi/checkoutPOSTDrive automated supermarket checkout loop.
catalogapi/catalogPOSTFull supermarket SKU catalog dump.
promotionsapi/promotionsPOSTExtract promoted products.

How do I authenticate with the Pepesto API?

Authentication is handled via an API key included in the 'Authorization' header using the 'Bearer' scheme (e.g., 'Authorization: Bearer pep_sk_...').

1. Get your credentials

The Pepesto API does not use a traditional developer dashboard for credential management. To obtain an API key, purchase a credit pack via the Pepesto website; immediately after the Stripe payment completes, perform a POST request to the /link endpoint with the email address you used at checkout. The API key is returned in the response. Note that the key is displayed only once, so store it securely. You can manage multiple keys for different projects by using the 'alias' field during checkout.

2. Add them to .dlt/secrets.toml

[sources.pepesto_source] PEPESTO_API_KEY = "pep_sk_your_key_here"

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 Pepesto 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 pepesto_pipeline.py

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

Pipeline pepesto_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pepesto_data The duckdb destination used duckdb:/pepesto.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 /parse and /catalog from the Pepesto 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 pepesto_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://s.pepesto.com/api/", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "catalog", "endpoint": {"path": "api/catalog"}}, {"name": "suggest", "endpoint": {"path": "api/suggest"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pepesto_pipeline", destination="duckdb", dataset_name="pepesto_data", ) load_info = pipeline.run(pepesto_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("pepesto_pipeline").dataset() sessions_df = data.catalog.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM pepesto_data.catalog LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("pepesto_pipeline").dataset() data.catalog.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 Pepesto 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 Pepesto?

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