Broker Connections

Open Broker connections to manage linked broker accounts.

- Interactive Brokers (IBKR) — full support via the dotQuant Desktop App: orders, live positions, and your own market-data entitlement on the chart.
- Trading 212 (T212) — full cloud-to-cloud support via your T212 API key: Invest and Stocks ISA accounts, fractional quantities, order status and fill polling with full economics (fill price, commission).

The portfolio lane executes on both: T212 directly, IBKR through the Desktop App — an IBKR portfolio's reviews and orders wait honestly while the desktop is offline, and IBKR's per-order commissions suit larger contribution slices than T212's commission-free model.

Each connection card shows its configuration state and live connectivity status. Credentials are write-only: once saved they are never returned to the browser — the settings form always shows empty credential fields by design. Archive a connection at any time from its card.

One connection at a time: every operation — an order, a cash read, a portfolio plan — names exactly one connection, and only that connection may serve it. A live account is never silently answered by a paper sibling, or the other way round.

IBKR integration keeps your trading sessions on your own machine. dotQuant servers communicate over WebSockets with the dotQuant Desktop App installed on your computer; the app forwards commands to your running IBKR TWS or IB Gateway instance.

Your IBKR credentials and API sessions never leave your local environment — the cloud side only ever sees order instructions and their results. The same bridge relays your entitlement's live market data to your chart (see Broker Live Bars and IBKR Market Data Subscriptions, which lists the subscription each region needs).

Connecting TWS is not enough on its own — IBKR has three independent switches that each silently block API orders. Run this checklist once and orders flow; miss one and an order sits in TWS untransmitted, showing a Transmit button and filling nothing.

1. TWS API access — TWS/Gateway: Global Configuration → API → Settings: enable ActiveX and Socket Clients, and make sure Read-Only API is unticked. Read-only lets dotQuant see data but blocks every order.

2. Client Portal Read-Only Access — Client Portal → Settings → Account Settings: if Read-Only Access is enabled for your user, no API order can be placed at all (TWS error 460, no trading permissions). Disable it — this is the most common blocker and the least visible one.

3. Trading Permissions — Client Portal → Settings → Trading Permissions: your account needs permission for the country/product you are trading (e.g. Stocks — Europe for a Xetra order). Missing permission also reports as error 460/201. Approval for a new permission can take a day.

After any change, restart TWS or Gateway — permissions and entitlements only take effect in a fresh session.

How a blocked order presents: in TWS it sits parked with a Transmit button (quantity 0/N); on dotQuant the marker shows Rejected with your broker's own reason and the matching fix. A rejected order is kept in your history — the reason is why.

Also worth knowing:
- The account allocation is pinned to the connection you placed the order on — with several IBKR accounts in one TWS, the order goes to the account you named in dotQuant, never a default.
- Market data subscriptions are a separate concern from trading permissions — see IBKR Market Data Subscriptions under Market Data & Charts.
- Paper accounts need TWS logged into the paper user (port 7497 by default); the desktop app connects to both live and paper TWS side by side.

The symbol view has Buy and Sell actions that open an order ticket for your connected broker account.

- Orders are passed through untouched: dotQuant never retries, amends, or auto-cancels an order on your behalf.
- Submission, acceptance, rejection, and fills stream back to the UI in real time.
- Your positions and account remain fully visible and manageable in TWS — dotQuant is a client of your broker, never a custodian.

For agents: the place-manual-order workflow covers the same path — sanity-check with get-broker-cash / get-broker-position, send submit-order (high-impact — confirm with the user), then follow the verdict on list-orders.

On a Buy you can tick Sell by the close. About 10 minutes before that market closes, dotQuant sends a market sell of what the buy filled — once, on the same connection, and never more than your account holds (if you sold some yourself, it sells only what is left; if you hold none, it sells nothing).

- The sale is an order of its own: it shows in Activity next to the buy, and in History as Sold by the close with what your broker made of it.
- If your broker refuses the sale (for IBKR: the Desktop App was not running), the position stays open overnight. History shows it as Order failed with the broker's reason, you are emailed, and dotQuant tries again in the next session's last minutes while the shares are still held — or sell them yourself.
- A buy still unfilled at the close has nothing to sell; whatever part fills later is sold at the end of the session it fills in.
- Markets that never close (crypto, FX) have no close to sell by.

For agents: submit-order with CloseBySessionEnd: true (buys only); the sale appears on list-orders with closesOrderId and closeReason, and on list-history as kind position-closed.

The Activity tab (under Portfolios) lists every order dotQuant ever sent for you — manual tickets, portfolio contributions, and strategy signals — with what your broker reported back.

- Filter chips split the list by origin: Portfolios, Strategies, Manual — each order carries the portfolio or strategy that produced it.
- Fills show quantity and price (plus commission where the broker reports it); rejections stay in the history with the broker's verbatim reason — a rejected order is a fact, not a failure to hide.
- Each symbol's feed view also carries a Transactions panel with your order history for just that instrument.

For agents: the list-orders query returns the same records, filterable by origin kind and reference.

dotQuant charges nothing on your trades — orders pass through to your broker untouched, and the commission you pay is your broker's own. What you pay depends on the fee plan selected on your IBKR account:

Fixed pricing (the default on many accounts) charges a percentage of trade value with a minimum per order — for example, European equities at ~0.05% with a €3.00 minimum (Xetra and other German venues). US stocks have their own fixed schedule (typically USD 0.005/share, USD 1.00 minimum).

Tiered pricing charges lower IBKR commissions (e.g. ~€1.25 minimum on Xetra) plus the exchange, clearing and regulatory fees passed through at cost. For most small orders it works out cheaper; for larger sizes compare both against IBKR's published schedules.

Small orders feel this the most. A €3.00 minimum on a €40 trade is 7.5% of the position — the price has to move that much before the trade breaks even. If you test with single shares, expect the minimum to dominate; switching the account to Tiered pricing (IBKR Client Portal → account settings → fee plan) usually softens it.

Where you see it in dotQuant: when your broker reports the commission with a fill, it appears on the order's chart marker, together with the realized P/L on closing trades — or, while the live broker price is streaming, the current P/L of the position the fill opened.

Fee figures above are IBKR's and were correct in mid-2026 — their published commission schedules are the authority.

Broker credentials are encrypted using AES-256 with keys managed in a secure Hardware Security Module (HSM). dotQuant employees cannot view your API keys, and they are only decrypted in memory during the brief moment required to send an order to your broker.

Write-only credentials: once saved, keys and secrets are never returned to the browser or displayed in clear text. To update credentials, enter new values and save — existing credentials remain active until replaced.