Is there a broker login?
No. Each integration is a file you export. The only read-only sync is an optional TopstepX key, and it cannot place, change, or cancel an order.
Integrations
Import the file your platform already exports.
Tiedbook does not connect to a broker password. You export the file the platform already offers, drop it on the preview, and read the skips before you save. Supported files rebuild round trips from fills. A repeated id is skipped. A working or canceled order is listed and left out of the book. Timestamps without a zone are read as America/Chicago, and the session still rolls at 5:00 PM. Beta files, including TradingView and Quantower, use the column mapper. The mapper attaches the columns you point at. It does not invent a price. After the fills are in, import Performance or the statement on Reconcile so the day can tie to the cent. The help center has the click path for each export. This index is the map: which file, which status, and what the preview is allowed to assume. Prop-firm names on a card mean the account can download that file. They are not affiliations, and the rule distance is not inside the CSV. If you trade more than one platform, each account keeps its own preset so an Apex Tradovate schedule is not applied to a NinjaTrader file by accident.
Supported
A finished parser. The preview should match the header you exported. If it does not, stop and do not confirm.
Tradovate
A Tradovate trading journal in Tiedbook starts from the Orders export and, when you have it, the Performance CSV. That is a file import. Tiedbook does not log in to Tradovate and does not auto-sync Tradovate.
TopstepX
A TopstepX trading journal can start from the trades CSV. Tiedbook also offers an optional read-only sync for TopstepX. That sync cannot place, change, or cancel an order. It is not an auto-sync for other platforms.
Rithmic
A Rithmic trading journal here means the R|Trader Pro Order History file. Filled and completed rows are kept. Tiedbook does not log in to Rithmic and does not auto-sync it.
NinjaTrader
A NinjaTrader trading journal in Tiedbook uses the NinjaTrader 8 Executions grid export. That file is supported. The Trade Performance export is Beta, because the columns are whichever ones you left visible.
ProjectX
A ProjectX journal file is supported when it uses the same column family as the TopstepX trade export: contract, entry, exit, prices, and fees or P&L. A different layout is left for the column mapper. This is a CSV import.
Sierra Chart
A Sierra Chart trading journal here uses the Trade Activity Log. Only rows whose activity type is Fill are imported. Tiedbook does not connect to Sierra Chart.
Beta
The column mapper is the import. Read every mapped field. A later export that renames a column needs another look.
TradingView
Tiedbook can open a TradingView paper or broker history CSV. That parser is Beta, because TradingView’s export is not one fixed set of columns. There is no TradingView auto-sync.
Quantower
Quantower is Beta. The preview looks for date, symbol, side, quantity, price, and connection. Map the columns yourself, and do not treat the import as a finished parser.
FAQ
What is Supported versus Beta?
Supported is a finished parser: Tradovate, NinjaTrader executions, Rithmic, TopstepX, Sierra Chart, and Interactive Brokers. Beta opens the column mapper and stays marked Beta until you confirm the preview.
Where do fees come from?
From the file when a commission cell is filled. From the dated preset on the account when the file omits them. Tradovate’s Orders export is the common case with no commission column.
Can I undo?
Yes. A confirmed batch can be removed without deleting the rest of the book. Nothing is stored until you confirm.
Start the 7-day trial. No card.
The preview names every skipped row before a fill is saved.