Review supported Bybit execution history with evidence
Use read-only access, validate leverage and fee fields returned by the source, and investigate patterns without outcome promises.
The diagnostic accepts broker CSV imports; automatic connections require a paid plan.
Bybit history can be split across spot and derivatives categories, with product-specific fields and retention. TradeInsights requests eligible spot and linear execution data. It does not need trading, transfer, or withdrawal permission.
Choose a supported Bybit import path
Uses read-only API credentials for eligible spot and linear execution history. Availability, history depth, fields, and timing vary by provider and account.
- 1
Create a read-only key
Create a dedicated Bybit system-generated API key and keep it read-only. Disable order, transfer, and withdrawal access.
- 2
Confirm product access
Check whether the target spot or linear account and region are available to the API key.
- 3
Import eligible executions
Connect on a paid plan and let TradeInsights request the history Bybit makes available to that key.
- 4
Reconcile the sample
Verify category, execution count, fees, timestamps, and closed-trade assembly against Bybit records.
What TradeInsights can use from Bybit
Only fields returned by the selected connection or export are imported. Reconcile counts and totals before relying on the analysis.
- Eligible spot and linear executions
- Symbol, side, quantity, price, and time
- Available execution-fee fields
- Order and category identifiers
- Closed-trade records where fills can be paired
- Import freshness and warning status
What your Bybit data unlocks
Turn imported records into an evidence-backed review loop
Reconcile before analysis
Compare the imported Bybit trade count, date range, and totals with the provider's own statement. Data warnings stay visible when the records are incomplete or stale.
Analyze useful segments
Break eligible closed trades down by category, symbol, side, time window, and tag. Results describe the imported sample; they do not predict future performance.
Inspect evidence behind a finding
When TradeInsights supports a leverage-adjacent or trade-frequency finding, review the method, confidence, limitations, and supporting trades before acting on it.
Close the review loop
Turn a supported finding into an explicit rule, then monitor later imported trades for adherence and new evidence.
Bybit analytics and import — FAQ
Is every Bybit account supported?
No. Availability can vary by provider, region, account type, product, and history endpoint. Check the live connection flow for the exact account before relying on automatic updates.
What access should I provide?
Create a separate Bybit API credential with read-only or view permissions. Leave trading, order placement, transfer, and withdrawal permissions disabled, and revoke the credential from Bybit if you stop using the connection.
How current will the imported data be?
Refresh timing and history depth depend on the selected provider and account. TradeInsights shows the latest successful update so you can verify freshness before reviewing a finding.
What if the connection is unavailable or incomplete?
Use an available Bybit export and File Import. Keep the API key read-only even if a product is not returned by the connection.
Can I evaluate the workflow before paying for a connection?
Yes. New accounts can import up to 30 real trades through the free diagnostic. The First Value Report requires at least 20 qualifying imported, closed trades. Ongoing connections and analytics require a paid plan.
Put your Bybit history into a repeatable review loop.
Start with a broker CSV, build an evidence-backed First Value Report, then upgrade for supported account sync, ongoing analytics, and guarded AI-assisted review.
Connection availability, imported fields, history depth, and refresh timing vary by provider. Verify imported data before relying on analytics.