Load Atlassian Commerce data in Python using dltHub

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

In this guide, we'll set up a complete Atlassian Commerce 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 atlassian_commerce_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.atlassian.com/commerce/api/v2", "auth": { "type": "bearer", "token": access_token, } }, "resources": [ "entitlements", "quotes" ], } [...] yield from rest_api_resources(config) def get_data() -> None: # Connect to destination pipeline = dlt.pipeline( pipeline_name='atlassian_commerce_pipeline', destination='duckdb', dataset_name='atlassian_commerce_data', ) # Load the data load_info = pipeline.run(atlassian_commerce_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 atlassian_commerce’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Quotes Endpoints: Endpoints related to managing quotes, including creating, retrieving, and updating quotes.

    • /commerce/api/v1/quotes: The first version of the quotes API.
    • /commerce/api/v2/quotes/{id}: The second version of the quotes API, allowing retrieval or modification of a specific quote by its ID.
    • /commerce/api/v3/quotes/{id}: The third version of the quotes API, offering potentially enhanced features for quote management.
  • Entitlements Endpoints: Endpoints for managing entitlements, which are permissions or rights associated with products or services.

    • /commerce/api/v2/entitlements/{entitlementId}: Endpoint for retrieving or managing a specific entitlement by its ID.
  • Versioning Endpoint: A generic endpoint that may provide information about the API versioning.

    • /commerce/api/{version}: Used to request the API based on a specific version number.

You will then debug the Atlassian Commerce 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:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install "dlt[workspace]"

    Initialize a dlt pipeline with Atlassian Commerce support.

    dlt init dlthub:atlassian_commerce duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Atlassian Commerce API, as specified in @atlassian_commerce-docs.yaml Start with endpoints entitlements and quotes and skip incremental loading for now. Place the code in atlassian_commerce_pipeline.py and name the pipeline atlassian_commerce_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 atlassian_commerce_pipeline.py and await further instructions.
  3. 🔒 Set up credentials

    The Commerce API requires a token for authentication, which you should generate as instructed in the authentication guidelines provided in the reference section.

    To get the appropriate API keys, please visit the original source at https://developer.atlassian.com/platform/commerce/rest/api-group-quotes/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

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

    python atlassian_commerce_pipeline.py

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

    Pipeline atlassian_commerce load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset atlassian_commerce_data The duckdb destination used duckdb:/atlassian_commerce.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
  5. 📈 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 atlassian_commerce_pipeline show
  6. 🐍 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("atlassian_commerce_pipeline").dataset() # get "entitlements" table as Pandas frame data."entitlements".df().head()

Extra resources:

Next steps