Create the IBKR route
Add an Interactive Brokers destination on the TradeJournal Pro website and copy its dedicated IBKR routing token.
Route supported US-stock instructions through TradeJournal Pro Desktop and the official local Client Portal Gateway. Start on paper, cap every signal by shares, and verify the final broker state—not only the parsed message.
Execution architecture
The website receives and parses the supported instruction.
Only the IBKR token can consume the stock execution queue.
A Windows PC or VPS must stay running and authenticated.
Broker order IDs, status, filled quantity, and average fill are reconciled.
This is not unattended provider-hosted IBKR execution. Login, 2FA, session keepalive, market permissions, and pacing rules still apply.
Add an Interactive Brokers destination on the TradeJournal Pro website and copy its dedicated IBKR routing token.
Run the official Client Portal Gateway locally, sign in with the paper-trading username, approve 2FA, and keep the session active.
Activate Desktop with the IBKR token, select the DU paper account, turn Paper only on, and begin with one share and a hard maximum of one.
Route one authorized Telegram channel, send a valid stock signal, and verify Desktop, TradeJournal Pro, and the final IBKR paper order.
Verified route · Desktop bridge 2.8.2
The public compatibility matrix remains the source of truth. Broker permissions, order rules, whole-share sizing, and the active market session can still limit a valid request.
Allowlisted US stocks and ETFs.
Supported stock flows; validate type and session.
Selected native bracket slices, subject to whole shares.
Working, partial, filled, cancelled, and rejected.
Absolute prices on tracked bracket orders.
One symbol or all routed IBKR stock positions.
Percentage command, normalized to whole shares.
No published trailing parity on the IBKR route.
Your IBKR username, password, and 2FA stay in the official Gateway login. TradeJournal Pro Desktop connects only to the HTTPS loopback Gateway and cannot redirect that authenticated session to a remote host.
Not for this individual-account route. Signal intake and routing use the website, but execution requires TradeJournal Pro Desktop plus the official Client Portal Gateway running and authenticated on your Windows PC or VPS.
No. Authentication stays on the official local IBKR Gateway page. TradeJournal Pro Desktop talks to the authenticated loopback Gateway; it does not collect your IBKR password or 2FA code.
No. The supported execution host is the Client Portal Gateway. TradeJournal Pro Desktop includes a read-only account view, while the separate IBKR Desktop trading interface is not the API host for this route.
IBKR stock quantities use whole shares in this safety profile. Five selected targets need at least five shares to create five one-share slices. With two shares, only two executable target slices can be created.
No. Accepted means IBKR returned order identifiers. Wait for the broker lifecycle status—working, partial, filled, cancelled, or rejected—and treat the official IBKR account as the final source of truth.
The safety profile manages orders and brackets it can identify and track. It will not silently cancel or modify unrelated manual orders, and it may stop a command when an untracked active order makes the result ambiguous.
Complete the connection test, send one valid signal during the intended session, and verify the broker-visible order plus a management command. Paper results still do not guarantee live fills.