Bybit Exchange Python API Docs | dltHub

Bybit is a cryptocurrency exchange platform providing REST and WebSocket APIs for market data, trading, account and asset management. The REST API base URL is https://api.bybit.com and All private endpoints require HMAC (or RSA) signature using X-BAPI-API-KEY, X-BAPI-SIGN and X-BAPI-TIMESTAMP 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 pip install "dlt[workspace]" 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:

---

How do I authenticate with the Bybit Exchange API?

Authenticated endpoints require an API key and secret. Each private request must include headers X-BAPI-API-KEY, X-BAPI-TIMESTAMP (ms), X-BAPI-SIGN (HMAC_SHA256 or RSA_SHA256 signature of timestamp+api_key+recv_window+queryString or jsonBodyString), and optional X-BAPI-RECV-WINDOW. Ensure local clock is NTP-synced and timestamp within server_time - recv_window and server_time + 1000.

1. Get your credentials

1. Log in to Bybit mainnet or testnet. 2) Navigate to User > API Management (https://www.bybit.com/app/user/api-management or https://testnet.bybit.com/app/user/api-management). 3) Create a new API key, choose permissions and whitelist IPs as needed. 4) Save the API key and secret securely (secret shown only once). 5) Use key+secret to compute request signatures.

2. Add them to .dlt/secrets.toml

Copy
[sources.bybit_exchange_source]
api_key = "your_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 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:

Copy
python bybit_exchange_pipeline.py

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

Copy
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:

Copy
dlt pipeline bybit_exchange_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 market_recent_trades and account_wallet_balance from the Bybit Exchange API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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": "market_recent_trades", "endpoint": {"path": "v5/market/recent-trade", "data_selector": "result.list"}},
            {"name": "account_wallet_balance", "endpoint": {"path": "v5/account/wallet/balance", "data_selector": "result.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):

Copy
import dlt

data = dlt.pipeline("bybit_exchange_pipeline").dataset()
sessions_df = data.market_recent_trades.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM bybit_exchange_data.market_recent_trades LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("bybit_exchange_pipeline").dataset()
data.market_recent_trades.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:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive retCode 10006 (invalid signature) or errors indicating timestamp/recv_window, verify: system clock is NTP-synced; X-BAPI-TIMESTAMP is milliseconds and within server_time - recv_window and server_time + 1000; X-BAPI-SIGN string is built as timestamp+api_key+recv_window+queryString (GET) or timestamp+api_key+recv_window+jsonBodyString (POST) and signed with HMAC_SHA256 producing lowercase hex. Include X-BAPI-RECV-WINDOW when needed.

Rate limits

Bybit enforces IP and API rate limits; retCode may indicate rate limit errors. Respect documented per-endpoint limits, implement exponential backoff and retries, and consider region-specific endpoints. Use small recv_window to reduce replay window but ensure network latency fits.

Pagination and data selectors

Most responses follow wrapper {retCode, retMsg, result, retExtInfo, time}. Lists are typically inside result.list or result.list / result (for some endpoints like instruments-info which may return list or instrument grouping). Spot instruments-info does not support pagination (limit & cursor invalid). Use returned cursor fields when present for cursor-based pagination.

Common error codes

0: success. 10001: parameter error. 10006: invalid signature. 10016: rate limit. (Also check retMsg for textual details.)

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack