Load Coinbase Advanced Trade data to DuckDB
Build a Coinbase Advanced Trade to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Coinbase Advanced Trade API base URL, auth, endpoints, and incremental loading.
Coinbase Advanced Trade REST API provides programmatic access to spot and derivatives market data, account information, and order management. Everything needed to build a working Coinbase Advanced Trade → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your Coinbase Advanced Trade to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Coinbase Advanced Trade to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Coinbase Advanced Trade API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
Coinbase Advanced Trade API at a glance
| Base URL | https://api.coinbase.com |
| Example endpoint | GET orders/historical/batch |
| Records found at | orders |
| Authentication | all authenticated requests require a Bearer token (JWT) — sent in the Authorization header, prefixed Bearer |
| Pagination | Cursor-based via cursor, next cursor at cursor (response field; also named cursor in request schema), page size via limit (default 49, max 250). For Advanced Trade REST list endpoints (e.g., List Orders), use cursor from the response to request subsequent pages. The response indicates additional pages via has_next. Pagination token is passed back as cursor query parameter; limit controls max results per call. |
| Incremental field | cursor |
| Record id | order_id |
| API reference | https://docs.cdp.coinbase.com/coinbase-app/authentication-authorization/api-key-authentication |
These values come from the Coinbase Advanced Trade API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Coinbase Advanced Trade API?
Requests are authenticated by signing a JWT with your API key's private key (using ES256 algorithm) and providing it in the 'Authorization' header as 'Bearer <JWT_TOKEN>'.
1. Get your credentials
To obtain API credentials for the Coinbase Advanced Trade API, navigate to the Coinbase Developer Platform (CDP) API Management page at https://portal.cdp.coinbase.com/projects/api-keys. Click 'Create API key', assign a name, and select the appropriate permissions (e.g., 'Trade' for placing orders). Under advanced settings, it is recommended to select 'Ed25519' as the signature algorithm. After completing 2FA, you will be provided with an API key and a secret file (or private key string). Note that for certain advanced setups or integrations, you may need separate keys for different portfolio types (e.g., Spot vs. Futures).
2. Add them to .dlt/secrets.toml
[sources.coinbase_advanced_trade_source] coinbase_api_key = "organizations/{org_id}/apiKeys/{key_id}" coinbase_api_secret = "-----BEGIN EC PRIVATE KEY-----\nYOUR_PRIVATE_KEY_HERE\n-----END EC PRIVATE KEY-----"
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What Coinbase Advanced Trade data can I load into DuckDB?
These are the Coinbase Advanced Trade endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts | /accounts | GET | accounts | List all accounts |
| products | /market/products | GET | products | List all products |
| orders | /orders/historical/batch | GET | orders | List historical orders |
| fills | /orders/historical/fills | GET | fills | List historical fills |
| portfolios | /portfolios | GET | portfolios | List all portfolios |
How do I load only new Coinbase Advanced Trade records?
Coinbase Advanced Trade exposes cursor on orders/historical/batch, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.
{"name": "orders", "endpoint": { "path": "orders/historical/batch", "data_selector": "orders", "incremental": {"cursor_path": "cursor", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated Coinbase Advanced Trade pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading /accounts and /orders from the Coinbase Advanced Trade API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def coinbase_advanced_trade_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.coinbase.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "orders", "endpoint": {"path": "orders/historical/batch", "data_selector": "orders"}}, {"name": "fills", "endpoint": {"path": "orders/historical/fills", "data_selector": "fills"}} ], } yield from rest_api_resources(config) def load_coinbase_advanced_trade_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="coinbase_advanced_trade_pipeline", destination="duckdb", dataset_name="coinbase_advanced_trade_data", ) load_info = pipeline.run(coinbase_advanced_trade_source()) print(load_info) if __name__ == "__main__": load_coinbase_advanced_trade_to_duckdb()
Run it with python coinbase_advanced_trade_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query Coinbase Advanced Trade data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("coinbase_advanced_trade_pipeline").dataset() df = data.orders.df() print(df.head())
SQL:
SELECT * FROM coinbase_advanced_trade_data.orders LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Coinbase Advanced Trade to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw Coinbase Advanced Trade loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Coinbase Advanced Trade data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for Coinbase Advanced Trade to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.