Article
Why IBKR Web API Data Can Look Different From TWS Chart Data
Understand why IBKR Web API data can look different from TWS chart data and how to build a reconciliation workflow before trusting automation.
IBKR Web API data can look different from TWS chart data because chart settings, data type, subscriptions, aggregation, timing, and session handling can all change what a trader sees. The workflow should reconcile those differences before the data feeds a journal, dashboard, or automation step.
Quick Answer
If IBKR Web API data does not match TWS chart data, do not assume one side is automatically wrong. First compare the exact symbol, exchange, bar size, session filter, what-to-show setting, timezone, and subscription status.
For structured AI review after the fields are stable, use Using Codex or Claude Code With IBKR Chart Data.
Reconciliation Checklist
A reconciliation workflow prevents silent data drift. It gives the trader a checklist before a mismatch becomes a bad dashboard, journal row, or automated decision.
The goal is to explain the mismatch before building on top of it.
| Check | Question to Ask | Review Output |
|---|---|---|
| Contract | Is the API contract the same instrument shown in TWS? | Confirmed symbol and exchange |
| Session | Are regular hours and extended hours handled the same way? | Session rule note |
| Bar type | Is the workflow using trades, midpoint, bid, ask, or another source? | Data type label |
| Timezone | Are timestamps normalized before comparison? | Timezone field |
| Aggregation | Are bars built from the same interval boundaries? | Bar-building rule |
| Subscription | Does the account have the needed market data access? | Coverage note |
Where MyLinedChart Fits
MyLinedChart does not replace IBKR data. It preserves the chart-review context around the data: drawn levels, notes, labels, setup tags, and review status.
That context helps a human compare what the API returned against what the trader actually reviewed on the chart.
Next Step
If the issue is request volume, use Fix IBKR Historical Data Pacing Violations in Your Workflow. If the issue is implementation handoff, use IBKR Chart Export Fields Codex Needs to Build Useful Trading Tools.
Do not let a mismatched data feed quietly become the source of truth.
FAQ
Why does IBKR Web API data look different from TWS chart data?
Differences can come from contract selection, session filters, bar type, aggregation rules, timestamps, subscriptions, or delayed versus live data.
What should I compare first?
Compare symbol, exchange, timeframe, session setting, what-to-show field, timezone, and the exact chart period.
Can AI fix mismatched IBKR data?
AI can help review fields and draft checks, but a human should verify the data source and chart match before using any output.
Sample Structured Chart-Data Exports
Review how chart drawings, annotations, OHLC, volume, and execution context become reusable structured data.