Triangle Platform Python API Docs | dltHub

Build a Triangle Platform-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The Triangle API uses API keys for authentication, with documentation available at https://www.triangleplatform.com/docs/api. The base URL is https://api.triangleplatform.com. Node.js library can be installed via npm. The REST API base URL is https://api.triangleplatform.com and all requests require an API key (supports Bearer or HTTP Basic).

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 Triangle Platform data in under 10 minutes.


What data can I load from Triangle Platform?

Here are some of the endpoints you can load from Triangle Platform:

ResourceEndpointMethodData selectorDescription
chains/v1/chainsGETitemsList all supported chains
chain/v1/chains/:idGETRetrieve a chain by id (object response)
networks/v1/networkGETitemsList all supported networks
network/v1/networks/:idGETRetrieve a network by id
vaults/v1/vaultsGETitemsList vaults (your vaults)
vault/v1/vaults/:idGETRetrieve a vault by id
wallets/v1/walletsGETitemsList wallets
wallet/v1/wallets/:idGETRetrieve a wallet by id
wallets_balance/v1/wallets/:id/balanceGETRetrieve native balance for a wallet (object)
wallets_tokens/v1/wallets/:id/tokensGETitemsList tokens for a wallet
accounts/v1/accountsGETitemsList accounts (your accounts)
account/v1/accounts/:idGETRetrieve an account by id
accounts_balance/v1/accounts/:id/balanceGETRetrieve native balance for an account (object)
accounts_tokens/v1/accounts/:id/tokensGETitemsList tokens for an account
accounts_nfts/v1/accounts/:id/nftsGETitemsList NFTs for an account
accounts_txs/v1/accounts/:id/txsGETitemsList transactions for an account
transactions/v1/transactionsGETitemsList all transactions (supports wallet filter)
transaction/v1/transactions/:idGETRetrieve a transaction by id
addresses/v1/addresses/:addressGETRetrieve address details (requires network param)
addresses_tokens/v1/addresses/:address/tokensGETitemsList tokens for an address (requires network param)
txs/v1/txs/:hashGETRetrieve a tx by hash (requires network param)
cryptocurrencies/v1/cryptocurrenciesGETitemsList all cryptocurrencies
cryptocurrency/v1/cryptocurrencies/:idGETRetrieve cryptocurrency by id
collections/v1/collectionsGETitemsList collections
collection/v1/collections/:idGETRetrieve a collection by id
markets/v1/marketsGETitemsList markets
market/v1/markets/:idGETRetrieve a market by id
listings/v1/listingsGETitemsList listings
listing/v1/listings/:idGETRetrieve a listing by id

How do I authenticate with the Triangle Platform API?

Triangle authenticates requests using API keys. You can either send the API key as a Bearer token in the Authorization header (Authorization: Bearer <API_KEY>) or provide the API key as the username in HTTP Basic auth (no password required).

1. Get your credentials

  1. Sign in to the Triangle Dashboard at https://dashboard.triangleplatform.com.
  2. Open the API keys / developer settings section.
  3. Create or copy an existing secret API key (keep it confidential).
  4. Use it as the Bearer token or as the Basic auth username when calling the API.

2. Add them to .dlt/secrets.toml

[sources.triangle_platform_source] api_key = "your_triangle_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 Triangle Platform 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 triangle_platform_pipeline.py

If everything is configured correctly, you'll see output like this:

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

Inspect your pipeline and data:

dlt pipeline triangle_platform_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 accounts and wallets from the Triangle Platform 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 triangle_platform_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.triangleplatform.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "accounts", "endpoint": {"path": "v1/accounts", "data_selector": "items"}}, {"name": "wallets", "endpoint": {"path": "v1/wallets", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="triangle_platform_pipeline", destination="duckdb", dataset_name="triangle_platform_data", ) load_info = pipeline.run(triangle_platform_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("triangle_platform_pipeline").dataset() sessions_df = data.accounts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM triangle_platform_data.accounts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("triangle_platform_pipeline").dataset() data.accounts.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 Triangle Platform data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Triangle Platform?

Request dlt skills, commands, AGENT.md files, and AI-native context.