Load Bybit Exchange data to DuckDB

Bybit is a cryptocurrency exchange platform providing REST API access for trading, market data, and account management. Everything needed to build a working Bybit Exchange → 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 Bybit Exchange 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 Bybit Exchange 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 Bybit Exchange 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.

---

Bybit Exchange API at a glance

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

---

How do I authenticate with the Bybit Exchange API?

Authenticated requests require HMAC-SHA256 signature-based authentication. Required HTTP headers include X-BAPI-API-KEY, X-BAPI-TIMESTAMP (in milliseconds), X-BAPI-SIGN, and X-BAPI-RECV-WINDOW.

1. Get your credentials

1. Log into your Bybit account via the web browser.
2. Click the user/profile icon in the top right corner and select API from the dropdown menu to navigate to the API Management page.
3. Click on the Create New Key button.
4. Choose the key type (System-generated for HMAC or Self-generated for RSA).
5. Configure permissions based on your requirements (e.g., Read-only, Trading).
6. Optionally, bind an IP address for enhanced security (IP whitelisting).
7. Complete the 2FA verification process.
8. Copy the API Key and API Secret immediately, as the secret will not be displayed again after you leave the screen.

2. Add them to .dlt/secrets.toml

Copy
[sources.bybit_exchange_source]
api_key = "your_api_key_here"
api_secret = "your_api_secret_here"
# If using IP whitelisting, ensure the originating server IP is configured in Bybit dashboard.

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

These are the Bybit Exchange endpoints dlt can load into DuckDB:

---

How do I load only new Bybit Exchange records?

Bybit Exchange exposes cursor on v5/order/history, 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": "order_history", "endpoint": {
    "path": "v5/order/history",
    "data_selector": "list",
    "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 Bybit Exchange pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v5/account/wallet-balance and /v5/order/create from the Bybit Exchange API into DuckDB:

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

@dlt.source
def bybit_exchange_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.bybit.com",
            "auth": {"type": "api_key", "api_key": api_key},
        },
        "resources": [
            {"name": "order_history", "endpoint": {"path": "v5/order/history", "data_selector": "list"}},
            {"name": "trade_history", "endpoint": {"path": "v5/execution/list", "data_selector": "list"}}
        ],
    }
    yield from rest_api_resources(config)


def load_bybit_exchange_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="bybit_exchange_pipeline",
        destination="duckdb",
        dataset_name="bybit_exchange_data",
    )
    load_info = pipeline.run(bybit_exchange_source())
    print(load_info)


if __name__ == "__main__":
    load_bybit_exchange_to_duckdb()

Run it with python bybit_exchange_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 Bybit Exchange 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("bybit_exchange_pipeline").dataset()
df = data.order_history.df()
print(df.head())

SQL:

Copy
SELECT * FROM bybit_exchange_data.order_history LIMIT 10;

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

---

How do I deploy the Bybit Exchange 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 Bybit Exchange 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 Bybit Exchange 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