Browse Brokers & importing trades

All topics

Import trades from TradingView

Upload the order history CSV from TradingView's Trading Panel for Paper Trading or a connected OANDA or Interactive Brokers account.

Same on every platform Updated
On this page

What this does

Brings Filled orders from the Order history CSV in TradingView’s Trading Panel into VEXA.

Before you start

  • TradingView is manual upload only. VEXA imports the CSV that TradingView exports; it does not connect to TradingView or your underlying broker through an API.
  • Upload the original .csv file, without renaming it. Other TradingView exports have different columns and cannot be detected as Order history, and for a connected broker the file name tells VEXA which broker it came from.
  • Overlapping periods are safe. Re-uploading an overlapping export does not create duplicate executions.
  • Choose the chart timezone. TradingView writes timestamps without a timezone, so VEXA needs the timezone selected on your chart when the orders were recorded.

Which TradingView accounts work

  • Paper Trading, from any TradingView version. Older exports that say Qty instead of Quantity, and exports with some columns hidden, work too.
  • OANDA connected to TradingView: OANDA One and OANDA Global Markets accounts (sized in lots) and v20 accounts (sized in units), for forex pairs, gold, silver, platinum and palladium, and index and energy CFDs such as US Wall St 30, UK 100, Brent and West Texas Oil.
  • Interactive Brokers connected to TradingView: stocks, futures and forex from the Trade History export. The export doesn’t name a stock’s exchange, so VEXA books stocks as US-listed shares in USD and says so in the upload result. If you trade stocks on other exchanges, import IBKR’s own Trades Flex Query instead.
  • Other connected brokers aren’t supported yet. Each broker writes its own columns and quantity unit (units, lots or contracts) into its export, so VEXA reads them one broker at a time. An export from another broker is named in the upload result and nothing is imported.

This is a file import from TradingView’s Trading Panel, not a broker API integration. The downloaded file name starts with paper-trading-order-history for Paper Trading, oanda-order-history for a connected OANDA account, or interactive-brokers-trade-history for Interactive Brokers.

The Account Summary, Closed Trades, Orders, Balance History and Positions tabs export balances, open orders and positions, not fills, so VEXA cannot import them.

Export and upload the CSV

Same on every platform

  1. In TradingView, open the Trading Panel at the bottom of the chart and select Paper Trading, or your connected OANDA or Interactive Brokers account.
  2. Open the Order History tab (for Interactive Brokers, the Trade History tab) and choose the period you want to import. For Paper Trading and OANDA, not Trade History, Balance History, Account Summary, Orders or Positions.
  3. Click the export icon in the panel’s toolbar and download the CSV. Don’t rename it: it starts with paper-trading-order-history for Paper Trading, oanda-order-history for OANDA, or interactive-brokers-trade-history for Interactive Brokers.
  4. Pick your chart timezone when uploading. TradingView does not write a timezone into the export, so Vexa reads the timestamps in the timezone you choose.
  5. In Vexa, choose TradingView → Manual upload and upload the CSV. Only Filled orders are imported; re-uploading an overlapping export is safe (duplicates are skipped).
  • Only Filled orders become trades — cancelled and rejected orders are ignored.
  • Commission is imported when TradingView records it; otherwise it is marked unknown rather than assumed to be zero.

Timezone

TradingView’s export carries no timezone. Pick the chart timezone that was active when the orders were recorded; VEXA interprets every placing and closing timestamp in the timezone you choose. The picker defaults to America/New_York, so change it when your chart used another timezone.

What is imported

VEXA imports Filled Paper Trading orders for:

  • Stocks and ETFs on the major exchanges, including the US, Canada, the UK, Europe, India, Japan, Hong Kong and Australia. London prices are in pence and Johannesburg prices in cents, and VEXA converts them to pounds and rand.
  • Forex, including crosses like GBP/JPY and EUR/CAD.
  • CFDs: metals, indices, energies, commodities and bonds on the broker feeds TradingView offers (for example FOREX.com, OANDA, Pepperstone, Capital.com, Eightcap and IC Markets).
  • Crypto spot and perpetual contracts.
  • Futures on CME, CBOT, NYMEX and COMEX (including the micro and mini contracts), ICE, Eurex and Cboe, both continuous (NQ1!) and dated (ESZ2026), sized by each contract’s point value.

Each trade is booked in the currency the instrument trades in (yen for GBP/JPY, euros for the DAX) and converted to your base currency.

From connected brokers, VEXA imports:

  • OANDA: forex pairs, gold, silver, platinum and palladium, and OANDA’s index and energy CFDs. OANDA One and Global Markets quantities are lots, converted to units with OANDA’s published lot sizes (100,000 for forex, 100 oz for gold, 1 for indices, 1,000 barrels for Brent and West Texas Oil); v20 quantities are already units. OANDA’s bond CFDs aren’t imported yet.
  • Interactive Brokers: stocks (booked as US-listed in USD), futures on CME, CBOT, NYMEX and COMEX sized by each contract’s point value, and forex pairs such as EUR.USD. Options aren’t imported yet. A commission on an instrument not priced in USD is recorded as 0 and noted, because the export doesn’t say which currency it was charged in.

Options aren’t imported yet. An instrument VEXA doesn’t recognise is skipped and named in the upload result, and the rest of the file still imports. Cancelled and rejected orders are ignored. An overlapping re-export is safe because VEXA skips duplicate executions.

Commission is imported when the CSV records it. If TradingView leaves commission blank, VEXA marks it unknown instead of assuming it was zero. Paper Trading charges commission in your account currency; when VEXA can’t convert it into the instrument’s currency, it records 0 and says so in the upload result.

If it doesn’t work

  • “This file isn’t a TradingView Order History export” or “This is a TradingView Account Summary export.” You exported the wrong Trading Panel tab. Return to the Order History tab for the selected account, click its export icon and upload that CSV unchanged. Chart-data exports, PDFs and edited or copy-pasted files can’t be imported.
  • “Trade History uploads are temporarily unavailable.” Upload the Order History export instead.
  • “This TradingView Order History has column names in another language.” Set TradingView’s language to English (profile menu, then Language), export the Order History tab again and upload that file.
  • “This TradingView export is missing columns VEXA needs.” You exported the Orders or Positions tab, or hid a column in Order History. Show every column in the Order History tab’s column settings and export again.
  • An instrument was skipped. The upload result names it and says why, and the rest of the file still imports. For OANDA accounts, VEXA imports forex pairs, metals and OANDA’s index and energy CFDs.
  • “This is OANDA’s Closed Trades list” or “This is TradingView’s Orders tab.” Those lists give profits or working orders, not fills. Export your OANDA account’s History tab instead.
  • Filled OANDA market orders have no Avg Fill Price. Some OANDA v20 TradingView exports leave the fill price blank, so VEXA cannot reconstruct those fills safely. Export the native Transaction History CSV from OANDA HUB and upload it under OANDA instead. See Import trades from OANDA.
  • “VEXA can’t import this broker’s TradingView export yet.” VEXA reads connected-broker exports from OANDA and Interactive Brokers so far. Upload your broker’s own trade report, or use VEXA AI Import.
  • “VEXA can’t find the columns it needs in this TradingView export.” A column is hidden or the export was renamed or edited. Show every column in the tab’s column settings, set TradingView to English, export again and upload the file unchanged, or use VEXA AI Import.
  • Times are off by hours. You picked the wrong timezone; delete the account’s trades and re-upload the CSV with the right one.

Broker page

Related

Still stuck? Email support@vexatrade.ai.