Load Buda data in Python using dltHub
Build a Buda-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.
In this guide, we'll set up a complete Buda 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 buda’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:
- Orders: Create, retrieve, and delete orders (POST, GET, DELETE /api/v2/orders)
- Tickers: Get market ticker information and price data (GET /api/v2/tickers)
- Balances: View account balances for all currencies or specific currency (GET /balances, /balances/
) - Currencies: Retrieve currency details, fees, and transaction information (GET /currencies/
, /fees/<transaction_type>) - Deposits: Manage and view deposit information for currencies (GET /currencies/
/deposits) - Withdrawals: Handle withdrawal operations and details (GET /currencies/
/withdrawals) - Banks: Access bank information for currency transactions (GET /currencies/{currency}/banks)
- Markets: Get market data and information (GET /markets)
You will then debug the Buda 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 Buda support.
dlt init dlthub:buda 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 Buda API, as specified in @buda-docs.yaml Start with endpoint(s) tickers and markets and skip incremental loading for now. Place the code in buda_pipeline.py and name the pipeline buda_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 buda_pipeline.py and await further instructions. -
🔒 Set up credentials
Buda.com uses API-KEY and API-SECRET authentication for private routes. Generate an API-KEY and API-SECRET from the account settings at https://www.buda.com/manejar_api_keys. Never share your API-SECRET.
To authenticate, sign all private requests by creating a nonce (integer, must be greater than the previous nonce; timestamp is recommended), then generate a signature string with the format "{METHOD} {path} {base64_encoded_body} {nonce}" where path includes query string but not host, base64_encoded_body is the request body encoded in Base64 (empty for GET requests), and nonce is the integer. The signature is computed from this string using your API-SECRET (the documentation cuts off but indicates HMAC is used based on context). Send the API-KEY, nonce, and signature in request headers when calling private routes.
To get the appropriate API keys, please visit the original source at api.buda.com.
If you want to protect your environment secrets in a production environment, look into [setting up credentials with dlt](https://dlthub.com/docs/walkthroughs/add_credentials).
4. 🏃♀️ Run the pipeline in the Python terminal in Cursor
```shell
python buda_pipeline.py
```
If your pipeline runs correctly, you’ll see something like the following:
```shell
Pipeline buda load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset buda_data
The duckdb destination used duckdb:/buda.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
```shell
dlt pipeline buda_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.
```python
import dlt
data = dlt.pipeline("buda_pipeline").dataset()
get tickers table as Pandas frame
data.tickers.df().head() ```