This guide explains the different historical bar sizes, the limited backfill of fine-resolution market data, the distinction between IBKR's wider API capabilities and the second-based snapshots used in our DataPumpBridge IB module, and why we maintain a separate local SQLite database.
Why We Chose Interactive Brokers for Market Data
IBKR offers access to many international exchanges and instrument classes from one broker environment. For someone already trading through Interactive Brokers, the option to reuse subscribed market data for chart analysis and backtesting is attractive. Costs vary by exchange, professional status and account. Some data packages have low monthly fees or qualifying commission-based waivers.
Availability across many markets does not mean unlimited historical coverage for every symbol. In particular, the broker's historical API can filter certain records and has restrictions for delisted securities and expired derivatives. The exact contract, exchange and the permissions attached to the account determine what the user can retrieve.
What Historical Data Does the IBKR API Provide?
The TWS API can connect through Trader Workstation (TWS) or IB Gateway and request eligible historical records. For bar data, reqHistoricalData uses a contract, time range, bar size and a value such as trades, bid, ask or midpoint. Depending on the market and request, a bar may include open, high, low, close and volume.
IBKR also documents a separate historical Time & Sales interface for trade and quote events. These are distinct API functions with different limitations. Our own integration is deliberately narrower: we work with second-based snapshots and do not promise that DataPumpBridge downloads a complete historical trade-by-trade tick stream.
For API users, correct request configuration matters as much as the nominal resolution. Specify the instrument identifier, eligible exchange, what-to-show price field, regular trading hours setting, requested duration and time zone consistently.
IBKR Historical Backfill: Seconds, Minutes, EOD and Ticks
There is no single historical data limit applicable to every data type. The broker's published API rules distinguish short-period historical bars from larger intraday bars and daily data. Tick-by-tick Time & Sales also has its own separate limits.
| IBKR historical category | Published or practical limitation | What it means for research |
|---|---|---|
| Bars of 1–30 seconds | Historical availability restricted to roughly the latest 6 months | Fine-grained history cannot be assumed available indefinitely |
| One-minute and larger intraday bars | No general fixed 6-month cutoff; actual history depends on instrument and source | Potentially longer research periods, subject to request limits |
| Daily end-of-day bars | No universal 6-month limit; instrument-specific historical coverage | Suitable for longer daily strategy studies when records exist |
| Historical tick Time & Sales | Separate API; documented lookback up to 3 years and normally up to 1,000 ticks requested per call | Does not describe the DataPumpBridge IB snapshot workflow |
The last row is provided only to clarify the broker's different products. We are not adding true-tick downloads to DataPumpBridge IB. A three-year tick lookback does not extend the six-month history rule for 1–30-second bars, because the requests refer to different datasets.
Always verify the current IBKR API documentation for an instrument and current entitlements. Published maximum periods are not guarantees of complete results.
Why Snapshots Are Not Genuine Tick Data
A snapshot represents a sample of the market at a point in time, or a time-bucketed observation depending on how the source is collected. A true tick event records an eligible trade or quote change. Several price changes can occur within a single second, and a snapshot does not preserve all of them.
For example, a stock might trade at 100.10, 100.25 and 100.15 in one second. A sampled quote cannot establish the exact sequence of these events. Even an OHLC bar for that second summarizes price activity rather than reproducing individual trades.
This difference becomes important for high-frequency backtesting or intrabar stop-and-target calculations. For our purposes, the IB snapshot workflow offers useful sampled intraday observations, while TaiPan is the DataPumpBridge source for genuine tick history when supported by the data subscription.
Historical One-Minute Data and Request Pacing
For minute bars and longer intervals, historical availability may extend further back than short second bars. However, IBKR still limits API calls by duration, pacing and service capacity. Downloading many years of one-minute data for numerous stocks usually requires a queue of smaller requests and careful checks for gaps and duplicates.
Official small-bar pacing restrictions include avoiding duplicate requests too close together, repeated requests for the same contract and price type within a short period, and excessive requests in a ten-minute window. Historical bid/ask requests can count more heavily toward applicable limits. Some larger-bar requests can still be slowed or rejected by the backend.
Our approach is to maintain an independent historical record and update incrementally where possible, rather than requesting the same stock history from the broker every time an analysis is performed.
End-of-Day Historical Prices and Market Coverage
Daily EOD data typically contains open, high, low, close and volume for each eligible trading session. This can be sufficient for swing trading, daily indicators and long-run portfolio research. IBKR does not impose the short second-bar lookback on all daily stock histories; the actual series may extend much further depending on instrument coverage.
There are exceptions. The broker has special historical limitations for delisted securities, some expired derivatives and certain products after exchange changes. Expired futures also have a limited historical availability window after expiry. Research into old stocks and futures contracts should therefore confirm actual returned dates rather than assuming the requested range will be complete.
Different providers can also report slightly different adjusted prices, volume or session boundaries. Backtesting requires understanding whether data are trades, quotes or midpoint-derived prices and whether corporate actions have changed the historical stock series.
Data Subscriptions and Pricing: An IBKR Advantage
Interactive Brokers can be economical for a customer who already maintains an account. Depending on jurisdiction, exchange and account classification, delayed or limited quotes may be complimentary, while additional real-time market data subscriptions are charged separately. Certain subscriptions offer fee waivers when qualifying trading commissions reach a published threshold.
Importantly, free delayed quotes do not automatically provide unrestricted historical API access. API history generally requires suitable market-data subscriptions. Professional subscribers may pay different exchange fees. The official market data pricing schedule provides the authoritative current terms.
We selected IBKR because the balance of broad market access and subscription options suits many research workflows, not because it has the deepest historical dataset or the smallest latency in every market.
Time Zones, Price Fields and Missing Records
Historical API calls should preserve time zone information and trading-session settings. A daily bar may be assigned to an exchange session rather than the local computer's calendar day. Daylight-saving changes can shift displayed chart times if dates are naively converted with a fixed offset.
For intraday analysis, distinguish TRADES, BID, ASK and MIDPOINT requests. Bid and ask are quotes, not necessarily completed trades. A backtest using midpoint prices without spread and slippage assumptions can appear more profitable than a realistic execution model.
Some historical trades are filtered by the broker's data service, and missing periods can reflect a closed exchange, an unsupported contract, incomplete permissions or unavailable source history. Use consistent request parameters and validate returned market data before importing them.
Why Our IB Snapshot History Is Stored in SQLite
DataPumpBridge keeps supported market observations in a separate local SQLite database, independent of the charting platform. This helps reduce repeated API backfill requests and allows a trader to continue using legitimately retained history for supported analysis workflows, subject to the broker's and exchanges' data-use permissions.
Incremental updates can append new or missing observations while retaining the source, contract, timestamp and price-field definition. Older prices can be revised or corrected, so the database also needs appropriate integrity checks and backups. Local technical storage does not itself create permanent rights to retain or redistribute licensed market data.
Because second-level history is time-limited, it makes sense to collect required observations while available. However, no application can reconstruct market events that were never provided in the first place.
How DataPumpBridge Compares Its Three Sources
| Source module | Resolution in our application | Main use |
|---|---|---|
| FreeQuotes | EOD stock prices only | Daily history and swing-trading strategies |
| Interactive Brokers | Second-based snapshots | Sampled intraday research across supported markets |
| TaiPan | True source-supported tick data | Event-sensitive research and detailed intraday histories |
These are intentional DataPumpBridge module distinctions, not a claim that every Interactive Brokers API is limited to snapshots. We do not plan a switch of our IB module to a tick-by-tick collection interface.
With NeuroShell Trader or as a Standalone Downloader
DataPumpBridge for NeuroShell Trader uses supported historical series to supply the trading platform and maintain independent local history. Our separate Data Downloader is designed for users of other analytical software who want SQLite storage and CSV/ASCII export without requiring NeuroShell Trader.
Each application includes FreeQuotes, TaiPan and IB under one annual license. Each costs €129 per year with a 14-day free trial. Payment and license activation take place inside the Windows application, not through a web checkout. See Prices and Licensing. External broker, exchange and data-provider fees are separate.
Frequently Asked Questions
How far back can I retrieve historical IBKR seconds data?
For the broker's short historical bars of 30 seconds or less, the published limitation is around six months. Exact data availability and entitlements vary by instrument.
How far back do IBKR one-minute bars go?
There is no general six-month hard cutoff for bars of one minute and larger. Actual backfill depth depends on the instrument, source data and request limits.
How much daily EOD stock history can the API retrieve?
There is no universal fixed range for all securities. The broker may provide years of daily history for eligible stocks, with restrictions for some delisted and expired products.
Are snapshots the same as historical tick data?
No. Snapshots are time-sampled market observations. Tick history describes individual eligible market events. IBKR provides a separate Time & Sales API, but that is not what DataPumpBridge's IB integration uses.
Are historical IBKR API downloads free?
They typically require appropriate market-data permissions, even where certain delayed quotes or selected brokerage data packages are complimentary.
What does local SQLite storage improve?
It helps maintain a consistent, reusable history and reduces unnecessary repeat requests when supported, while preserving the need to respect broker and exchange licenses.