Load Dapr data in Python using dltHub
Build a Dapr-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.
In this guide, we'll set up a complete Dapr 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
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 dapr_metadata_api’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:
-
Metadata Endpoints:
/v1.0/metadata: General metadata access./v1.0/metadata/myDemoAttribute: Access specific metadata attributes.
-
Actors Endpoints:
/v1.0/actors: Manage actors./v1.0/actors/myactor/50/method/getData: Invoke a method on a specific actor.
-
State Store Endpoints:
/v1.0/state/statestore/name: Access a specific state store by name./v1.0/state/statestore: General state store management./v1.0/state/statestore/key1: Access a specific key in the state store./v1.0/state/statestore/transaction: Manage transactions within the state store./v1.0/state/statestore/bulk: Bulk operations on the state store.
-
Secrets Endpoints:
/v1.0/secrets/my-secret-store/my-secret: Access specific secrets from a secret store.
-
Invoke Endpoints:
/v1.0/invoke/nodeapp/method/neworder: Invoke a method on a specific application./v1.0/invoke/cart/method/add: Add items to a cart in the application./v1.0/invoke/cart.production/method/add: Add items to the production cart in the application.
-
Publish Endpoints:
/v1.0/publish/pubsub/deathStarStatus: Publish messages to a topic./v1.0/publish/pubsub/TOPIC_A?metadata.ttlInSeconds=120: Publish to a topic with TTL metadata./v1.0/publish/pubsub/TOPIC_A?metadata.rawPayload=true: Publish raw payloads to a topic.
You will then debug the Dapr 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
dltWorkspaceInstall dlt with duckdb support:
pip install "dlt[workspace]"Initialize a dlt pipeline with Dapr support.
dlt init dlthub:dapr_metadata_api duckdbThe
initcommand will setup the necessary files and folders for the next step. -
🤠 Start LLM-assisted coding
Here’s a prompt to get you started:
PromptPlease generate a REST API Source for Dapr API, as specified in @dapr_metadata_api-docs.yaml Start with endpoints add` and add and skip incremental loading for now. Place the code in dapr_metadata_api_pipeline.py and name the pipeline dapr_metadata_api_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 dapr_metadata_api_pipeline.py and await further instructions. -
🔒 Set up credentials
The snippets mention that you can authenticate to Azure by following the guidelines provided in the Azure authentication documentation, but they do not specify any requirements for keys, tokens, client IDs, client secrets, headers, token URLs, or flows.
To get the appropriate API keys, please visit the original source at https://v1-11.docs.dapr.io/reference/api/metadata_api/. 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 dapr_metadata_api_pipeline.pyIf your pipeline runs correctly, you’ll see something like the following:
Pipeline dapr_metadata_api load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset dapr_metadata_api_data The duckdb destination used duckdb:/dapr_metadata_api.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 dapr_metadata_api_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("dapr_metadata_api_pipeline").dataset() # get "add`" table as Pandas frame data."add`".df().head()