IBKR Flex Query and Wolfora

IBKR Activity Statements are excellent for taxes and audits. They are awkward as a living portfolio feed: formats change, date windows are easy to get wrong, and weekly manual downloads do not match how you actually trade.

Flex Web Service lets you define a reusable query (trades, cash transactions, and related activity) and pull it with a token and query ID. Wolfora stores those secrets encrypted and syncs on your behalf so history stays current.

Flex is especially strong for deposits, withdrawals and fills that some live portfolio APIs omit, delay, or format differently. Pair Flex for history with optional live marks when you want fresher valuations between Flex runs.

In IBKR Account Management you create a Flex Web Service token (think of it as a password for machine retrieval) and one or more Flex Queries that describe which sections and date logic you need.

Wolfora asks for the token and the query ID tied to the query that includes at least trades and cash. Without cash, performance after funding events will lie. Without trades, positions drift from reality.

This path is read-oriented for portfolio reconstruction. You are not granting Wolfora a mandate to trade; you are allowing statement-like data to be fetched into your Wolfora brokerage account.

In IBKR Account Management, enable Flex Web Service and generate a token. Store it like a password — anyone with token + query ID can pull the configured statement data.

Create a Flex Query that includes the activity you care about: trades and cash at minimum. Add other sections only if you understand them; noisy queries are harder to debug.

In Wolfora Portfolio setup, open IBKR and paste the token and query ID. In production, when prompted for live OAuth material, paste PEM content as instructed — do not rely on local disk paths that exist only on your laptop.

Run the first sync. Confirm a known deposit and a known trade appear under your IBKR-linked Wolfora account. If the query window is too narrow, widen it in IBKR and sync again.

If the same mental “brokerage” account previously lived at Trade Republic or another neo-broker, import that older history into the correct Wolfora account (or keep accounts separate on purpose). Charts should start at the real economic beginning, not at the IBKR transfer date alone.

Re-run sync after funding days, large trades, or corporate actions. Flex is periodic truth; it is not a millisecond blotter.

Keep IBKR as the execution venue and Wolfora as the consolidation layer. When numbers disagree, IBKR statements win for executions; then fix mapping or query scope in Wolfora.

IBKR is rarely your only French envelope. PEA often stays at a bank or another broker; Saxo may host a second CTO or PEA. Use separate Wolfora accounts per venue/envelope, then the global view for net worth and allocation. See the PEA vs brokerage and Saxo guides for the other pillars.

Do not merge PEA and IBKR into one Wolfora account just to “simplify”. You will lose tax-envelope clarity the first time you ask “how much is in the PEA?”

Query too narrow: you only pull the last month and wonder why inception charts look empty. Widen the historical window once, then keep an incremental habit.

Cash omitted: trades sync but deposits do not, so returns after funding look miraculous or catastrophic. Always include cash transactions.

Token rotated in IBKR but not updated in Wolfora: sync fails quietly until you paste the new token.

Mixing advisory, joint, or multiple IBKR accounts into one Flex query without labelling: start simple — one clear brokerage story per Wolfora account — then expand.