Load CoinDCX data to DuckDB

CoinDCX is a cryptocurrency exchange platform that provides a REST API for accessing market data and managing trading accounts. Everything needed to build a working CoinDCX → 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 CoinDCX to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from CoinDCX 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 CoinDCX 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.

---

CoinDCX API at a glance

These values come from the CoinDCX API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the CoinDCX API?

All private endpoints require an API key and an HMAC-SHA256 signature passed in the X-AUTH-APIKEY and X-AUTH-SIGNATURE headers, respectively. The signature is generated by hashing the JSON-encoded payload with the API secret.

1. Get your credentials

To obtain your CoinDCX API credentials: 1. Log in to your CoinDCX account. 2. Navigate to your profile section and select 'API Dashboard'. 3. Click the 'Create API key' (or 'Create New One') button. 4. Enter a label/name for the key and choose whether to bind the key to a specific IP address. 5. Complete the security verification steps (typically via email and SMS or Google Authenticator OTP). 6. After confirmation, the API Key and Secret will be displayed on the screen. Be sure to copy and store the Secret key immediately, as it will be hidden after you refresh or navigate away from the page.

2. Add them to .dlt/secrets.toml

Copy
[sources.coindcx_source]
api_key = "your_api_key_here"
api_secret = "your_api_secret_here"

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 CoinDCX data can I load into DuckDB?

These are the CoinDCX endpoints dlt can load into DuckDB:

---

How do I load only new CoinDCX records?

CoinDCX exposes page on exchange/v1/derivatives/futures/positions, 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.

Copy
{"name": "futures_positions", "endpoint": {
    "path": "exchange/v1/derivatives/futures/positions",
    "incremental": {"cursor_path": "page", "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 CoinDCX pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading orders and markets from the CoinDCX API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def coindcx_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.coindcx.com",
            "auth": {"type": "api_key", "api_key": api_key, "name": "X-AUTH-APIKEY", "location": "header"},
        },
        "resources": [
            {"name": "futures_positions", "endpoint": {"path": "exchange/v1/derivatives/futures/positions"}},
            {"name": "futures_orders", "endpoint": {"path": "exchange/v1/derivatives/futures/orders"}}
        ],
    }
    yield from rest_api_resources(config)


def load_coindcx_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="coindcx_pipeline",
        destination="duckdb",
        dataset_name="coindcx_data",
    )
    load_info = pipeline.run(coindcx_source())
    print(load_info)


if __name__ == "__main__":
    load_coindcx_to_duckdb()

Run it with python coindcx_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 CoinDCX 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):

Copy
import dlt

data = dlt.pipeline("coindcx_pipeline").dataset()
df = data.futures_positions.df()
print(df.head())

SQL:

Copy
SELECT * FROM coindcx_data.futures_positions LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the CoinDCX 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 CoinDCX loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load CoinDCX data to?

dlt loads into any of these — only the destination argument changes:

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack