Propeller Commerce Python API Docs | dltHub

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

Last updated:

Propeller Commerce is a commerce platform providing REST APIs for bulk import/export and management of e-commerce resources including products, orders, and inventory. The REST API base URL is https://api.helice.cloud and All requests require an OAuth 2.0 access token used as a Bearer token..

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


What data can I load from Propeller Commerce?

Here are some of the endpoints you can load from Propeller Commerce:

ResourceEndpointMethodData selectorDescription
products/v2/productsGETdataRetrieve products (paginated)
orders/v2/ordersGETdataRetrieve orders (supports expands and search)
inventory/v2/inventoryGETdataRetrieve inventory resources (paginated)
users/v2/usersGETdataRetrieve users
usergroups/v2/usergroupsGETusergroupsRetrieve user groups

How do I authenticate with the Propeller Commerce API?

Authentication is performed via OAuth 2.0 client credentials flow by POSTing client_id and client_secret to obtain an access_token, which is then sent as a Bearer token in the Authorization header of API requests.

1. Get your credentials

  1. Sign in to your Propeller/Helice admin or developer portal and navigate to the API client or application management section. 2. Create a new API client or application. 3. Note the provided client_id and client_secret generated by the system. 4. Use these credentials to request an access token via a POST request to https://api.helice.cloud/oauth2/token with grant_type=client_credentials. 5. Include the returned access_token as a Bearer token in the Authorization header for all subsequent API requests.

2. Add them to .dlt/secrets.toml

[sources.propeller_commerce_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 Propeller Commerce 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 propeller_commerce_pipeline.py

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

Pipeline propeller_commerce_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset propeller_commerce_data The duckdb destination used duckdb:/propeller_commerce.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 products and orders from the Propeller Commerce 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 propeller_commerce_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.helice.cloud", "auth": {"type": "bearer", "token": client_secret}, }, "resources": [ {"name": "products", "endpoint": {"path": "v2/products", "data_selector": "data"}}, {"name": "orders", "endpoint": {"path": "v2/orders", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="propeller_commerce_pipeline", destination="duckdb", dataset_name="propeller_commerce_data", ) load_info = pipeline.run(propeller_commerce_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("propeller_commerce_pipeline").dataset() sessions_df = data.products.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM propeller_commerce_data.products LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("propeller_commerce_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 Propeller Commerce 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 Propeller Commerce?

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

Available Pipelines