Bigcommerce Python API Docs | dltHub
Build a Bigcommerce-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
BigCommerce is a SaaS e-commerce platform providing REST APIs for store administration, catalog management, and order processing. The REST API base URL is https://api.bigcommerce.com/stores/{store_hash}/v3 and all requests require an X-Auth-Token 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 Bigcommerce data in under 10 minutes.
What data can I load from Bigcommerce?
Here are some of the endpoints you can load from Bigcommerce:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| products | /v3/catalog/products | GET | data | Retrieve all products in the catalog |
| customers | /v3/customers | GET | data | Retrieve all registered customers |
| price_lists | /v3/pricelists | GET | data | Retrieve all price lists |
| orders | /v2/orders | GET | Retrieve all store orders | |
| categories | /v3/catalog/categories | GET | data | Retrieve all product categories |
How do I authenticate with the Bigcommerce API?
BigCommerce REST APIs require an 'X-Auth-Token' header containing your API account access token. Requests must also include 'Accept: application/json' and 'Content-Type: application/json' headers.
1. Get your credentials
- Log in to your BigCommerce Control Panel as a user with Store Owner permissions. 2. Navigate to Settings, then select Store-level API accounts. 3. Click the + Create API Account button. 4. Select V2/V3 API token as the token type. 5. Enter a name for the integration. 6. Set the required OAuth scopes for your application. 7. Click Save. 8. A pop-up will appear displaying your API credentials (Client ID, Client Secret, and Access Token) and the API Path. Immediately copy these values or download the provided .txt file, as this information cannot be viewed again once the pop-up is closed.
2. Add them to .dlt/secrets.toml
[sources.bigcommerce_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 Bigcommerce 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 bigcommerce_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bigcommerce_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bigcommerce_data The duckdb destination used duckdb:/bigcommerce.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 v3 and v2 from the Bigcommerce 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 bigcommerce_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.bigcommerce.com/stores/{store_hash}/v3", "auth": {"type": "api_key", "api_key": access_token, "name": "X-Auth-Token", "location": "header"}, }, "resources": [ {"name": "products", "endpoint": {"path": "v3/catalog/products", "data_selector": "data"}}, {"name": "customers", "endpoint": {"path": "v3/customers", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bigcommerce_pipeline", destination="duckdb", dataset_name="bigcommerce_data", ) load_info = pipeline.run(bigcommerce_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("bigcommerce_pipeline").dataset() sessions_df = data.products.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bigcommerce_data.products LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bigcommerce_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 Bigcommerce data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Bigcommerce?
Request dlt skills, commands, AGENT.md files, and AI-native context.