Terra Python API Docs | dltHub
Build a Terra-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Terra's REST API documentation is available at https://docs.terra.money/develop/endpoints. For live dApps, use private RPC endpoints. Swagger API documentation is found at https://docs.terra.money/develop/swagger. The REST API base URL is https://phoenix-lcd.terra.dev, https://pisco-lcd.terra.dev, https://api.tryterra.co/v2 and All public LCD GET endpoints require no authentication; TryTerra API uses an API key/Bearer token for authenticated endpoints..
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 pip install "dlt[workspace]" and start loading Terra data in under 10 minutes.
What data can I load from Terra?
Here are some of the endpoints you can load from Terra:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| terra_alliances | /terra/alliances | GET | alliances | Query all alliances (paginated) |
| terra_alliances_delegations | /terra/alliances/delegations | GET | delegations | Query alliance delegations (paginated) |
| cosmwasm_codes | /cosmwasm/wasm/v1/code | GET | code_ids | Get metadata for stored wasm codes |
| cosmwasm_contracts_by_code | /cosmwasm/wasm/v1/code/{code_id}/contracts | GET | contracts | List smart contracts for code id |
| blocks_latest | /cosmos/base/tendermint/v1beta1/blocks/latest | GET | block | Get latest block |
| account | /cosmos/auth/v1beta1/accounts/{address} | GET | account | Get account details by address |
| validators_latest | /cosmos/base/tendermint/v1beta1/validatorsets/latest | GET | validators | Get latest validator set |
| proposals | /cosmos/gov/v1beta1/proposals | GET | proposals | List governance proposals |
| node_info | /cosmos/base/tendermint/v1beta1/node_info | GET | default_node_info | Get node info |
| ibc_fee_enabled | /ibc/apps/fee/v1/fee_enabled | GET | fee_enabled_channels | List fee‑enabled IBC channels |
How do I authenticate with the Terra API?
Terra LCD endpoints (phoenix/pisco) are public read‑only REST endpoints — no API key required for GET queries. TryTerra endpoints use an API key sent as an Authorization: Bearer header or an api_key header depending on endpoint documentation.
1. Get your credentials
- For Terra mainnet/testnet LCD: no credentials needed to call GET endpoints. Use the public LCD base URLs above.
- For TryTerra (api.tryterra.co): sign up at https://tryterra.co (or the provider dashboard), create an API key/token in the developer settings. Copy the token and use it as Authorization: Bearer .
2. Add them to .dlt/secrets.toml
[sources.terra_source] api_key = "your_tryterra_api_key_here"
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 Terra 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:
python terra_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline terra_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset terra_data The duckdb destination used duckdb:/terra.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline terra_pipeline 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 terra_alliances and blocks_latest from the Terra 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 terra_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://phoenix-lcd.terra.dev, https://pisco-lcd.terra.dev, https://api.tryterra.co/v2", "auth": { "type": "bearer", "api_key": api_key, }, }, "resources": [ {"name": "terra_alliances", "endpoint": {"path": "terra/alliances", "data_selector": "alliances"}}, {"name": "blocks_latest", "endpoint": {"path": "cosmos/base/tendermint/v1beta1/blocks/latest", "data_selector": "block"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="terra_pipeline", destination="duckdb", dataset_name="terra_data", ) load_info = pipeline.run(terra_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("terra_pipeline").dataset() sessions_df = data.terra_alliances.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM terra_data.terra_alliances LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("terra_pipeline").dataset() data.terra_alliances.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 Terra 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 Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Terra?
Request dlt skills, commands, AGENT.md files, and AI-native context.