Tradier trading journal

About this integration

Tradier is popular with options-heavy retail traders, and the Tradier connection in TFQ is not options-aware: the sync keeps equity fills and drops option fills before they reach your journal. If options are why you use Tradier, note that there is no Tradier CSV preset: an upload lands on the generic mapping, which derives P&L by pairing fills and, where your file carries no realised-P&L column it recognises, reads the contract multiplier off the symbol: an option row whose symbol cell carries the full contract code (“AAPL 240315C00180000”) imports at ×100, while one carrying only the underlying ticker imports at 1/100th. Tradier is also reachable via SnapTrade, which records the ×100 — that is the options path, or log them by hand. The other thing to know before connecting: the authorize request asks for `read,trade`, so the credential we store is allowed to submit orders. Nothing in this product ever submits one — but that restraint is written in our code, not imposed by Tradier's grant.

Supported instruments

Access scope

TFQ calls two Tradier endpoints: `/v1/user/profile` to find your account numbers, and that account's `/history` filtered to trade events. It never reads your positions, your balances, or your open orders — and of the trade events it does read, it keeps only those whose `trade_type` is Equity, so option fills are discarded before they reach your journal. The token Tradier issues reaches further than the reading we do: the authorize request asks for `read,trade`, so the credential we store is allowed to submit orders. Nothing in this product ever submits one — but that restraint is written in our code, not imposed by Tradier's grant.

What we read is limited by our code, not by Tradier. TradeFlow Quantum has no order-placement code path and we do not intend to add one — but because the granted token carries trade permission, treat a compromise of TFQ as reaching this brokerage connection. If that is not an acceptable risk, use the CSV import instead of connecting.

Setup

1. 1System → Brokers → Connect Tradier
2. 2Sign in to Tradier and approve the scope — it includes trade, not read alone
3. 3Redirect back, then click Sync — pulling the last 90 days of equity fills takes ~45 seconds

How the Tradier connection syncs

Authorization

OAuth 2.0 — authorize at api.tradier.com/v1/oauth/authorize, exchange at /v1/oauth/accesstoken.

API host

api.tradier.com for live accounts, sandbox.tradier.com for sandbox accounts.

Account lookup

GET /v1/user/profile runs first — the account number is read out of the profile before any history call.

Data endpoint

GET /v1/accounts/{account}/history with type=trade, limit=200.

Round-trip pairing

Separate FIFO queues per symbol per side. A buy closes the oldest open short or opens a long; a sell closes the oldest open long or opens a short.

Re-sync safety

Each fill gets a deterministic id built from its date, symbol, quantity, price, cash amount and a per-symbol sequence number, so re-syncing the same history cannot duplicate trades.

Tradier import caveats

• —A history call returns at most 200 events.
• —Tradier signs the quantity rather than naming the side, so direction is inferred: a positive quantity is a buy, a negative one is a sell.

Why use TradeFlow Quantum instead of Tradier's built-in tools?

• ✓Cross-broker view. If you trade Tradier plus any other broker, TFQ unifies the equity curve, P&L attribution, and mistake-checker across all of them.
• ✓Mistake-checker on YOUR data — surfaces patterns in your Tradier history (time-of-day, setup type, emotional state) the broker won’t show you.
• ✓Long-term data ownership. Tradier’s built-in analytics typically limit history to 90 days or 1 year. TFQ keeps every trade for as long as your account exists, exportable any time — closed trades as CSV, everything including open positions as a JSON backup.