IBKR integration
How does the FillScope IBKR trading journal work?
FillScope requests a user-configured IBKR Flex report, parses the returned statement, and stores normalized records for analysis.
1. What must the trader configure?
The trader creates an IBKR Flex Query that contains the required trade and position sections, then provides its Flex token and query ID to FillScope. The query controls which fields and dates IBKR makes available.
2. How is a report requested?
FillScope uses the IBKR Flex Web Service request endpoint to obtain a statement reference, polls the statement endpoint, parses the XML response, and records the statement period and import health.
3. What happens to imported rows?
Trade rows are normalized into account-scoped records. Repeated rows use the account user and IBKR trade ID as the update key, so refreshed reports update matching imported records instead of intentionally creating a second copy.
4. Is this a real-time execution feed?
No. FillScope does not receive live executions from TWS or IB Gateway. It refreshes configured Flex reports through the Flex Web Service. Data freshness therefore depends on IBKR report availability, the selected statement period, refresh scheduling, cooldowns, and successful parsing.
5. What can make an import incomplete?
Missing settings, an expired or invalid token, a query with the wrong sections, IBKR report delay, statement-format changes, network failure, or a row-level database error can make an import fail or finish partially. FillScope records run status, statement dates, row totals, written rows, and failures so the user can review import health.
Is FillScope affiliated with IBKR?
FillScope is not affiliated with Interactive Brokers. IBKR availability, data definitions, report fields, limits, and service behavior are controlled by Interactive Brokers and may change.