OTTO Market Python API Docs | dltHub

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

Last updated:

OTTO Market REST API provides programmatic access for sellers and service partners to manage products, orders, and other marketplace operations. The REST API base URL is https://api.otto.market and all requests require a Bearer token in the Authorization header.

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


What data can I load from OTTO Market?

Here are some of the endpoints you can load from OTTO Market:

ResourceEndpointMethodData selectorDescription
orders/v4/ordersGETList of orders filtered by fulfillment state
availability/v1/availability/quantitiesGETresourcesGet quantities from a partner
product_delivery_info/v1/availability/product-delivery-informationGETresourcesGet product delivery information from a partner
price_reductions/v1/price-reductionsGETGet all price reductions for a partner
products/v5/productsGETRead product variations

How do I authenticate with the OTTO Market API?

Authentication requires an access token (specifically an installation access token for service partners) provided in the Authorization header as a Bearer token. Requests must include an 'Authorization' header with the value 'Bearer {access_token}'.

1. Get your credentials

  1. Register for an account on the OTTO Partner Connect (OPC) portal. 2. Once your account is approved and verified, navigate to the API Access section within OPC. 3. Create a new application (Self-App) to generate your credentials. 4. Upon successful creation, the dashboard will display your Client ID, Client Secret, and App ID. Copy and securely store these values immediately, as they are required to authenticate with the OTTO Market API.

2. Add them to .dlt/secrets.toml

[sources.otto_market_source] access_token = "REPLACE_ME"

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 OTTO Market 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 otto_market_pipeline.py

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

Pipeline otto_market_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset otto_market_data The duckdb destination used duckdb:/otto_market.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 /v1/token and /v1/apps/{appId}/installations/{installationId}/accessToken from the OTTO Market 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 otto_market_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.otto.market", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "availability", "endpoint": {"path": "v1/availability/quantities", "data_selector": "resources"}}, {"name": "product_delivery_info", "endpoint": {"path": "v1/availability/product-delivery-information", "data_selector": "resources"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="otto_market_pipeline", destination="duckdb", dataset_name="otto_market_data", ) load_info = pipeline.run(otto_market_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("otto_market_pipeline").dataset() sessions_df = data.availability.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM otto_market_data.availability LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("otto_market_pipeline").dataset() data.availability.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 OTTO Market 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 OTTO Market?

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