Importing with Bridge

The sidebar lists the sources under Trade import. Which ones you see depends on your plan.

Source	Where the data comes from
Tradervue	The Tradervue API, using your Tradervue username and password
Interactive Brokers	A Flex Query over the web, or the TWS API from a running Trader Workstation or IB Gateway
DAS Trader Pro	A local socket connection to DAS Trader Pro
Test	Synthetic executions you build or generate, for checking the pipeline

Every panel follows the same shape: fetch from the source, look at the preview, then send. Nothing is uploaded without you pressing a button.

When Bridge is paired and connected, an Account picker at the top of the panel selects which account alias the data belongs to. If it does not match the alias selected on the Import screen in your browser, Bridge warns you rather than guessing.

The Tradervue panel imports trades and their executions from your Tradervue account.

Setup is in Bridge Settings, tab Brokers, section TraderVue: your Username and Password, with Test to confirm the credentials work, Hide to mask them, and Clear Credentials to remove them.

In the panel itself:

1. Pick a Date range.
2. Fetch executions pulls the trades in that range and their fills.
3. Review the preview.
4. Import to TraderReflex uploads, or Send to web import pushes it to the browser for the normal preview and confirm flow.

This is the migration path if you have history in Tradervue. Import in reasonable date ranges rather than everything at once, and check the first range carefully before pulling years of it.

Interactive Brokers has two routes, shown as tabs: Flex Query and TWS sync.

Flex Query uses the IB Flex Web Service. Configure it in Bridge Settings, Brokers, Interactive Brokers Flex Query, with a Token and a Query ID from your IB account management. Then choose a Date range and Fetch executions. The preview can be toggled between Orders and Fills.

Use Flex Query for history. It works without any local software running and it is the reliable route for backfilling.

TWS sync connects to a running Trader Workstation or IB Gateway through the local API. Configure the connection in Settings, Brokers, TWS Connection, with Host, Port, and Client ID. This route reads the current day's executions.

Use TWS sync for today. It requires the platform to be running and API access enabled in TWS, and it will not see days that are no longer in the platform's session.

DAS Trader Pro connects over a local socket. Configure it in Bridge Settings, Brokers, DAS Trader Pro: Host, Port, Account, Username, Password, and Test Connection. The default host and port point at DAS running on the same machine.

The panel has two tabs. Import pulls today's executed orders and converts them into the internal format. The preview shows Time, Symbol, Side, Size, and Price. From there, Import to TraderReflex or Send to web import.

DAS must be running and configured to accept the connection. If the test fails, that is where to look first, before anything in TraderReflex.

Every broker panel offers the same two destinations, and the choice matters.

Import to TraderReflex uploads straight into your trade log using the credentials pairing gave Bridge. It is fewer clicks.

Send to web import pushes the converted data to the Import screen in your browser, where it appears exactly like a dropped file: the same preview, the same trades and executions toggle, the same duplicate detection, and the same Confirm import. Nothing is written until you confirm there.

Use Send to web import by default, especially the first few times with a new source. The preview is where you catch a converter reading a column wrong, and once executions are in the log, removing them takes the advanced removal tool.

If Bridge sends data while you are on another screen, the web app offers a dialog titled Import from desktop, explaining that the Trade Import app sent data to review, with Go to Import or Not now.

Account aliases must agree. If Bridge has one alias selected and the Import screen has another, Bridge blocks the send rather than filing the trades in the wrong book. There is also a confirmation dialog showing which alias the web Import has selected.

The Test panel builds synthetic executions. It is there so you can verify the whole path (Bridge, the hub, the preview, the import, the analytics refresh) without waiting for real trades.

You can add rows by hand with Symbol, Side, Size, Price, and Comm, clone and split fills, close positions, and generate whole trade cycles with Generate Trade Cycles by choosing a Number of trade cycles. Executions can be saved to and loaded from storage.

Then Import to TraderReflex or Send to web import as usual.

The honest warning: synthetic executions are indistinguishable from real ones once imported. Use a separate account alias for anything you generate here, so you never have to work out later which trades were yours.