Bybit Exchange Python API Docs | dltHub

Build a Bybit Exchange-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Bybit is a cryptocurrency exchange platform providing REST API access for trading, market data, and account management. The REST API base URL is https://api.bybit.com and all requests to private endpoints require HMAC-SHA256 authenticated headers.

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 add "dlt[hub]" and start loading Bybit Exchange data in under 10 minutes.


What data can I load from Bybit Exchange?

Here are some of the endpoints you can load from Bybit Exchange:

ResourceEndpointMethodData selectorDescription
order_history/v5/order/historyGETlistRetrieve historical order records
open_orders/v5/order/realtimeGETlistRetrieve current open order records
trade_history/v5/execution/listGETlistRetrieve historical trade records
position_list/v5/position/listGETlistRetrieve current position information
instrument_info/v5/market/instruments-infoGETlistRetrieve market instrument information
transaction_log/v5/account/transaction-logGETlistRetrieve account transaction history

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

[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 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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Bybit Exchange 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:

uv run python bybit_exchange_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 /v5/account/wallet-balance and /v5/order/create from the Bybit Exchange 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 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 get_data() -> 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)

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("bybit_exchange_pipeline").dataset() sessions_df = data.order_history.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM bybit_exchange_data.order_history LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("bybit_exchange_pipeline").dataset() data.order_history.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 Bybit Exchange 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 harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Bybit Exchange?

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

Available Pipelines