Correction Window

A correction window is the period during which market data records, such as trades or OHLCV candles, may still be updated to fix late, missing, or inaccurate information.

A correction window is the period during which market data records may still be revised after they are first published. In crypto market data, correction windows are used to handle late-arriving trades, exchange-side corrections, missing messages, backfilled data, and other updates that can affect historical records.

A correction window defines how long a data provider may continue to update a record after its original event time or reporting interval has passed. For example, an OHLCV candle may be published shortly after a one-minute period closes, but it may remain subject to correction for a short time if additional trades arrive late or if an exchange later sends corrected data.

Correction windows help separate fast preliminary publication from final historical accuracy. A short correction window supports low-latency applications, while a longer correction window gives more time to reconcile incomplete or delayed data.

Correction windows matter because market data is not always complete the moment a period closes. Exchanges can deliver data out of order, network delays can occur, and downstream systems may detect inconsistencies after an initial value has already been published.

Without a correction window, systems may treat provisional data as final too early. That can lead to inaccurate backtests, mismatched candles, incorrect volume calculations, or inconsistent analytics across different data snapshots.

For OHLCV data, a correction window determines when an open, high, low, close, or volume value may still change. During this period, late trades or corrected trade records can update candle values. After the correction window closes, the candle is generally treated as final unless a later backfill or historical correction process is performed.

This is especially important for high-frequency trading, analytics pipelines, and compliance workflows that depend on knowing whether a candle is provisional or final.

The appropriate correction window depends on the market, exchange, asset class, and use case. Real-time dashboards may use short windows to keep data fresh, while research, backtesting, and reporting systems may prefer longer windows to maximize historical accuracy.

A robust data pipeline should document the correction window it uses and track when records were first published, updated, and considered final.

Suppose a one-minute BTC/USD candle closes at 12:01:00. The data provider publishes an initial candle immediately after close. At 12:01:08, a trade from the 12:00:00 to 12:01:00 interval arrives late and changes the high price and total volume. If the provider uses a 30-second correction window, the candle can still be updated until 12:01:30. After that point, it is treated as final for most downstream consumers.

CoinAPI Market Data API provides access to real-time and historical market data across crypto exchanges. Understanding correction windows helps developers design systems that can distinguish between provisional market data and finalized historical records. This is important when building OHLCV pipelines, backtesting engines, trading dashboards, reconciliation workflows, and analytics products.

Crypto API made simple: Try now or speak to our sales team