How do I get my Bybit API key?
Log into your Bybit account.
Hover over the user icon, in the upper-right corner, to display the drop-down menu and select "API".
Then select "Create New Key" (System-generated API Keys).
Select the "API Transaction" box and enter a unique name for your API Key.
Do not use IP whitelisting.
Grant the API key permissions "Orders", "Positions", "Trade", "Account Transfer", and "Subaccount Transfer" as shown in the image below and enable strictly the "Read-Only" option.
Click on "Confirm" and enter your Google Authenticator password.
To import your data, you must first create an Integration in the Blockpit Web App.
To do so, click + Integration in the upper navigation.Select Bybit from the list of exchanges, and then copy the API key and the secret into the designated fields. Confirm your entries by clicking Continue.
❗ Your API key will have to be renewed every 3 months. You can edit the Integration and renew your API key there.
💡 When using subaccounts, each subaccount must be imported into a separate Blockpit Integration. To do this, you must create a new Blockpit Integration using a special subaccount API key (Subaccount→ API Management).
❗ Bybit EU is not currently supported via API key. A standalone integration via API is already in the works.
Which data can be imported via Bybit API?
Your complete transaction history always serves as the basis for your tax report. Preferably, automatic API solutions are used to import your transactions. Our team is committed to implementing all API data provided by your exchange for you.
Using the following list, you can identify all products that are implemented:
Transactions
📆 Classic Account: Spot Market Trades older than 365 days are not available via API.
📆 Unified V1 & V2 Account: Conversions before May 2024 and Transfers, Spot Market Trades & Derivative PnL/Fee transactions older than 720 days (2 years) are not available via API.
Supported
✅ Crypto Deposits & Withdrawals
✅ Fees
✅ Refunds & Cashbacks
✅ Conversions
✅ Spot Market Trades
✅ Leverage Token Trades
✅ Derivative Trades PnL (Profit, Loss, Fee and Funding)
In case of missing transactions, you can help our support team via chat-request to include them in our import spectrum (if technically possible).
Not Supported
⛔ Fiat Deposits & Withdrawals
⛔ Margin Trading
⛔ Trading Bot
⛔ Buy Crypto (Express, P2P)
⛔ Margin Trading
⛔ Conversions
⛔ Airdrops
⛔ Flexible Savings
⛔ Liquidity Mining
⛔ Dual Assets
⛔ Shark Fin
⛔ Launchpool
⛔ Copy Trading
❗ Bybit does not provide data for delisted assets and trading pairs via API.
Missing transactions can be found by comparing the actual history of your exchange. You can add these subsequently as individual manual entries or by migrating your CSV data into our Excel template.
Example: Add missing transactions of delisted assets
Example: Add missing transactions of delisted assets
You can find delisted assets under the following link in the menu item "Delistings".
Search the transaction history of your exchange for delisted assets or trading pairs and make a comparison with all CSV files provided by your exchange.
Then add the missing transactions to your Blockpit integration, either one by one or aggregated batch:
Bybit-Derivatives-ClosedPNL.csv
Example: Add missing P&L transactions from futures and derivative trading
Example: Add missing P&L transactions from futures and derivative trading
More information in the following article:
Synced Balance
Supported
✅ All Account Balances
Not Supported
👁🗨 Bybit Saving Account Balance (only Funding Account Balance available)
Assets in the saving account are temporarily (until the saving process is exited) not fully displayed in the Synced Balance of your Blockpit integration. However, this has no effect on the tax report, as no internal outflows (transactions) occur in the integration. The resulting Tip: Mismatched Balance can be ignored in this context. The “Reconcile Balance” function should not be used in this exceptional case!
If your Synced Balance is displayed incompletely, you can help our support team via chat-request to include it in our import spectrum (if technically possible).
How do I solve problems with my Bybit Integration?