Load commercetools data in Python using dltHub

Build a commercetools-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Commercetools data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def commercetools_migration_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.{region}.commercetools.com/{projectKey}/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            me, carts, types
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='commercetools_migration_pipeline',
        destination='duckdb',
        dataset_name='commercetools_migration_data', 
    )
    # Load the data
    load_info = pipeline.run(commercetools_migration_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

Accelerate pipeline development with AI-native context
Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
Build Python notebooks for end users of your data
Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from commercetools_migration’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

General: General API operations including resource management and retrieval.
Authentication: OAuth 2.0 authentication and token management.
Products: Management of product listings, types, and variants.
Orders: Creation, management, and retrieval of orders.
Customers: Customer management including creation and updates.
Carts: Cart operations including creation, updates, and retrieval.
Discounts: Management of discounts, discount codes, and promotions.
Import: High-speed import operations for various resources.

You will then debug the Commercetools pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

We suggest using a model like Claude 3.7 Sonnet or better
Index the REST API Source tutorial: https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api/ and add it to context as @dlt rest api
Read our full steps on setting up Cursor

Now you're ready to get started!

⚙️ Set up dlt Workspace

Install dlt with duckdb support:
```
pip install "dlt[workspace]"
```
Initialize a dlt pipeline with Commercetools support.
```
dlt init dlthub:commercetools_migration duckdb
```
The init command will setup the necessary files and folders for the next step.

🤠 Start LLM-assisted coding

Here’s a prompt to get you started:

Prompt
Please generate a REST API Source for Commercetools API, as specified in @commercetools_migration-docs.yaml 
Start with endpoints me and  and skip incremental loading for now. 
Place the code in commercetools_migration_pipeline.py and name the pipeline commercetools_migration_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python commercetools_migration_pipeline.py and await further instructions.

🔒 Set up credentials

The Commercetools API requires OAuth 2.0 for authentication, utilizing access tokens that must be included in the Authorization header of each request. Tokens expire in 48 hours, and proper scopes must be granted for accessing various resources.

To get the appropriate API keys, please visit the original source at https://www.commercetools.com/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

🏃‍♀️ Run the pipeline in the Python terminal in Cursor


python commercetools_migration_pipeline.py

If your pipeline runs correctly, you’ll see something like the following:


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

📈 Debug your pipeline and data with the Pipeline Dashboard

Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:
- Pipeline overview: State, load metrics
- Data’s schema: tables, columns, types, hints
- You can query the data itself
```
dlt pipeline commercetools_migration_pipeline show
```
🐍 Build a Notebook with data explorations and reports

With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.
```
import dlt

data = dlt.pipeline("commercetools_migration_pipeline").dataset()
# get  table as Pandas frame
data..df().head()
```

Running into errors?

It's important to note that the Import API is designed for high-speed and large-volume operations, but does not allow resource deletions. Additionally, the API follows the Command Query Responsibility Segregation (CQRS) pattern, and every request must include a projectKey. Rate limits are enforced to protect against abuse, so managing API call frequency is crucial to avoid errors like 'TooManyRequests'. Also, responses may not be immediate due to operational delays during peak loads.

Extra resources:

Learn more with our 1h LLM-assisted coding course!