Candle Finality

Candle finality is the point when an OHLCV candle is no longer expected to change because all market data for its time interval has been processed.

back to all terms

Candle finality describes when an OHLCV candle has moved from a provisional state to a final state. An OHLCV candle summarizes the open, high, low, close, and volume for a specific market and time interval. Before finality, those values may still change as late trades, corrections, or exchange updates are processed.

After finality, the candle is treated as stable for historical analysis, backtesting, charting, and downstream data pipelines. This matters because real-time market data often arrives in stages. A data provider may publish a one-minute candle as soon as the minute closes, but the provider may still need time to process all trade messages for that interval. Some exchanges send updates after the close of the candle period, and some corrections may arrive after the first version of the candle is visible. During that period, the candle is useful for live monitoring, but it should not always be treated as a final historical record. Once finality is reached, teams can use the candle with more confidence in reports, analytics, strategy testing, and stored datasets. CoinAPI users should distinguish between provisional candles used for live applications and final candles used for historical reporting or automated analysis.

Candle finality helps teams avoid using unstable OHLCV values in systems that require repeatable results. It is especially important for backtesting, data warehousing, compliance reporting, charting, and automated analysis where small changes in historical data can affect conclusions.

In crypto market data, candle finality means that a candle has passed the point where its OHLCV values are expected to keep changing. This is different from simply reaching the end of the time interval. A candle can close at 12:01:00 for a one-minute period, but the data provider may still be processing late or corrected trades for that same minute. Until that processing is complete, the candle may be provisional. Finality gives users a practical signal that the candle can be treated as part of the historical record. This distinction helps developers decide which data is suitable for live dashboards and which data is suitable for stored analytics.

An OHLCV candle can change after the interval closes because market data systems need to process messages that may not arrive in perfect order. Exchanges can send trades, cancellations, corrections, or delayed updates after the first candle value has already been calculated. Network latency, exchange-specific reporting behavior, and reconciliation logic can also affect when the complete set of trades is available. If a late trade has a price above the previous high or below the previous low, the high or low can change. If additional trades are included, the volume can also change. This is why users should understand whether they are viewing provisional candles or final candles.

Developers should treat live candles and final historical candles as different data states. Live candles are useful for monitoring current market activity, updating charts, and triggering time-sensitive workflows. Final candles are better suited for backtesting, historical research, audit trails, and production analytics that need stable inputs. A common approach is to store provisional data quickly, then update or replace it after the finality window has passed. Teams should also document how their system handles late-arriving market data and correction windows. This reduces confusion when a candle seen in real time differs from the finalized candle retrieved later.

A trading dashboard shows a BTC/USD one-minute candle immediately after 10:00:59 ends. At first, the candle shows a close price of $64,200 and volume of 18 BTC. A few seconds later, the market data provider processes late trades from the same minute, changing the high, close, and volume. Once the post-close reconciliation is complete, the candle is marked or treated as final, and that finalized version is used for backtesting and historical charts.

CoinAPI Market Data API helps teams access cryptocurrency market data, including OHLCV data, across many exchanges through consistent API formats. For workflows that depend on candle finality, users should separate real-time monitoring from finalized historical analysis and account for late-arriving market data. This allows trading systems, research pipelines, and reporting tools to use the right candle state for the right purpose.

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

Start for FreeGet in Touch