Criteo retail media Python API Docs | dltHub

Build a Criteo retail media-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Criteo Retail Media API provides a suite of tools for advertisers to create, launch, and monitor media campaigns across platforms. The REST API base URL is https://api.criteo.com/<version>/retail-media/ and all requests require a Bearer token obtained via OAuth 2.0 flow.

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 Criteo retail media data in under 10 minutes.


What data can I load from Criteo retail media?

Here are some of the endpoints you can load from Criteo retail media:

ResourceEndpointMethodData selectorDescription
accounts/accountsGETLists all Accounts associated with your API credentials
retailers/accounts/{accountId}/retailersGETdataLists all Retailers associated with the Account
campaigns/accounts/{accountId}/campaignsGETdataLists all Campaigns within the Account
line_items/accounts/{accountId}/line-itemsGETLists all Line Items within the Account
pages/retailers/{retailerId}/pagesGETList all Pages associated with the Retailer

How do I authenticate with the Criteo retail media API?

Criteo uses OAuth 2.0 to generate a Bearer token, which must be included in the Authorization header of all API requests as 'Authorization: Bearer <access_token>'.

1. Get your credentials

  1. Log in to the Criteo Partner Dashboard (https://partners.criteo.com). 2. Navigate to the My Apps section. 3. Select your desired application or click the + button to create a new one. 4. In the application settings, click Create new key. 5. A text file containing your API Key (client_id) and API Secret (client_secret) will be automatically downloaded. Store this file securely, as the API Secret cannot be retrieved again from the dashboard.

2. Add them to .dlt/secrets.toml

[sources.criteo_retail_media_source] client_id = "your_api_key_from_downloaded_file" client_secret = "your_api_secret_from_downloaded_file"

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 Criteo retail media 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 criteo_retail_media_pipeline.py

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

Pipeline criteo_retail_media_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset criteo_retail_media_data The duckdb destination used duckdb:/criteo_retail_media.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 /accounts and /campaigns from the Criteo retail media 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 criteo_retail_media_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.criteo.com/<version>/retail-media/", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "retailers", "endpoint": {"path": "accounts/{accountId}/retailers", "data_selector": "data"}}, {"name": "campaigns", "endpoint": {"path": "accounts/{accountId}/campaigns", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="criteo_retail_media_pipeline", destination="duckdb", dataset_name="criteo_retail_media_data", ) load_info = pipeline.run(criteo_retail_media_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("criteo_retail_media_pipeline").dataset() sessions_df = data.retailers.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM criteo_retail_media_data.retailers LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("criteo_retail_media_pipeline").dataset() data.retailers.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 Criteo retail media 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 Criteo retail media?

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