Saleor Python API Docs | dltHub

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

Last updated:

Saleor uses GraphQL APIs for communication, with both public and private endpoints for store operations. The Saleor API is accessed via /graphql/ and requires POST requests. Saleor's GraphQL Playground provides an interactive API editor. The REST API base URL is https://your-saleor-store.com/graphql/ and All requests to the Saleor GraphQL API require a Bearer token for authentication, passed 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 pip install "dlt[workspace]" and start loading Saleor data in under 10 minutes.


What data can I load from Saleor?

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

ResourceEndpointMethodData selectorDescription
products/graphql/POSTdata.products.edges[].nodeFetches a list of products
orders/graphql/POSTdata.orders.edges[].nodeFetches a list of orders
customers/graphql/POSTdata.users.edges[].nodeFetches a list of customers (users)
collections/graphql/POSTdata.collections.edges[].nodeFetches a list of product collections
categories/graphql/POSTdata.categories.edges[].nodeFetches a list of product categories

How do I authenticate with the Saleor API?

Authentication for the Saleor GraphQL API is done using Bearer tokens, which must be included in the Authorization header of HTTP requests.

1. Get your credentials

  1. Access your Saleor storefront or dashboard.
  2. Use the tokenCreate GraphQL mutation, providing your email and password, to obtain a user authentication token. For example, using a GraphQL client, execute a mutation like:
mutation TokenCreate($email: String!, $password: String!) { tokenCreate(email: $email, password: $password) { token refreshToken errors { message } } }
  1. The token returned in the response is your authentication credential. For Saleor Apps, long-lived tokens are generated during app installation.

2. Add them to .dlt/secrets.toml

[sources.saleor_source] token = "your_bearer_token_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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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 Saleor 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:

python saleor_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline saleor_pipeline 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 products and orders from the Saleor 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 saleor_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://your-saleor-store.com/graphql/", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "products", "endpoint": {"path": "graphql/", "data_selector": "data.products.edges[].node"}}, {"name": "orders", "endpoint": {"path": "graphql/", "data_selector": "data.orders.edges[].node"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="saleor_pipeline", destination="duckdb", dataset_name="saleor_data", ) load_info = pipeline.run(saleor_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("saleor_pipeline").dataset() sessions_df = data.products.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM saleor_data.products LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("saleor_pipeline").dataset() data.products.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 Saleor 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 Workbench:

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

Was this page helpful?

Community Hub

Need more dlt context for Saleor?

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