Browse Brokers & importing trades

All topics

Connect Bybit

Bybit syncs hourly with a read-only API key. For file imports, VEXA accepts the established Trade History exports and a limited Unified Trading Account Transaction Log route for ETH options.

Same on every platform Updated
On this page

What this does

Bybit syncs automatically once connected, pulling every hour. It covers spot, linear and inverse derivatives, and options.

Before you start

  • Read-only permissions. Account read is required, orders read is required, positions read is useful. Do not enable trading or withdrawal on the key you give VEXA.
  • The secret is shown once. Copy it immediately.
  • Bybit EU works too. If you trade on bybit.eu, create the key there. VEXA checks your key against Bybit Global and Bybit EU and connects to the right one.
  • The API reaches 180 days. Files reach two years.
  • Timezones. VEXA treats Bybit API and Trade History timestamps as UTC. Bybit’s retail export guide does not state the timezone for the Unified Trading Account Transaction Log; VEXA also interprets that file’s Time column as UTC.

Set up the automatic sync

Same on every platform

  1. In Bybit, open your account menu and go to API Management.
  2. Choose Create New Key and pick the API transaction type.
  3. Set the permissions to read only.
  4. Complete the verification step.
  5. Copy the key and the secret.
  6. In VEXA, open the Bybit page and paste both, then save.

Steps

Same on every platform

Download Trade History for older history

  1. In Bybit, open Orders, then Unified Trading Order.
  2. Pick the product tab: Spot or Futures (derivatives). Options export separately.
  3. Choose Trade History, not Order History. Trade History lists every fill; Order History lists orders, including ones that never filled, and VEXA cannot rebuild trades from it.
  4. Set the date range. Bybit allows up to six months per export within the last two years, and up to 10,000 rows per file.
  5. Click Export and download the CSV.
  6. Upload it to VEXA.
  7. Repeat for each product type you trade, and for each six-month window.

Or download the Unified Trading Account Transaction Log for supported option fills

  1. In Bybit, open Assets, then Unified Trading Account.
  2. Open History Records, choose Transaction Log, then click Export.
  3. Select the date range and click Export Now to generate the CSV. From this page, Bybit allows up to six months per export within the last two years, with up to 10,000 entries per file.
  4. Download the CSV, leave it unchanged, and upload it to VEXA.
  5. Use this route only for TRADE rows for USDT-settled ETH options. Other products are not supported from this report yet.

Limits and gotchas

  • Closed P&L exports are accepted for USDT and USDC perpetuals. Each closed position row becomes one trade, with P&L and fees exactly as Bybit reports them. Entry times are approximate because Bybit does not include the position’s open time. Trade History is the better export when available; Bybit allows it for the last two years.
  • Transaction Log support is deliberately narrow. VEXA imports only TRADE rows for USDT-settled ETH options. Transfers are skipped. Other products and settlement, funding, or delivery rows are skipped with a warning instead of being turned into trades.
  • Transaction Log option quantity is in coin units. VEXA uses a multiplier of 1 for these supported rows. A negative Fee Paid value is a cost and is imported as a positive commission expense.
  • The retail Transaction Log timezone is not documented by Bybit. VEXA interprets the file’s Time column as UTC. The UTC+0 statement in Bybit’s institutional-reporting guide applies to institutional reports and does not establish the retail export’s timezone.
  • Three exports, not one. A derivatives trader who exports only spot gets an import with almost nothing in it, and no error to explain why. See Some of my trades are missing.
  • Trade History, not Order History. The Order History file is a list of orders and is not an import format.
  • A file with only a header row means the date range had no fills. Widen the range and export again.
  • Fees are read from the file, so profits are net. A fee charged in a coin the file never prices is kept at zero and flagged in the import result rather than guessed.
  • Funding rows are skipped. The derivatives Trade History includes funding-fee rows (Filled Type “Funding”); they are not fills and are not booked as trades or fees.
  • Times are UTC to the minute. The derivatives export has no seconds, so fills in the same minute keep the file’s order.
  • A spot balance you are still holding is an open position. VEXA shows it in Portfolio rather than as a closed trade.

What you should see

After connecting, an Active badge and a first pull, then a last-sync time that advances hourly.

After an upload, a result panel naming the detected Bybit format, once per file.

If it doesn’t work

  • The key was rejected. The permission set is wrong, or the secret was truncated when you copied it.
  • Most of your trades are missing. You may have uploaded only one Trade History product type, or a Transaction Log containing rows outside the limited supported option subset. Export the other Trade History files you need and review any import warnings.
  • Trades look shifted by a few hours. VEXA interprets Bybit timestamps as UTC, including the retail Transaction Log’s undocumented Time field. Set your display timezone rather than re-importing.

Broker page

Related

Still stuck? Email support@vexatrade.ai.