OHLCV Period Boundary
An OHLCV period boundary is the exact start or end timestamp that defines which trades belong inside a specific open, high, low, close, and volume candle.
OHLCV candles aggregate trades into fixed time intervals such as one minute, five minutes, one hour, or one day. Each interval has a defined start time and end time. These timestamps are the period boundaries of the candle.
For example, a one-minute candle for 12:00:00 to 12:01:00 includes market activity from the start boundary at 12:00:00 up to, but not including, the next boundary at 12:01:00. The next candle begins exactly at 12:01:00. This boundary logic prevents trades from being counted in two candles or excluded from both.
Clear OHLCV period boundaries are especially important when comparing data across exchanges, rebuilding historical candles, calculating indicators, or reconciling candles with raw trades. If systems use different boundary conventions, the same trade stream can produce different open, high, low, close, or volume values.
Why OHLCV Period Boundaries Matter
OHLCV period boundaries matter because they define the membership rules for candle data. A single trade near the boundary can change the close of one candle, the open of the next candle, the high or low, and the reported volume.
Consistent period boundaries help ensure that analytics, backtests, trading signals, dashboards, and historical datasets use the same time-bucketing logic. They also make it easier to compare candles from APIs, exchanges, and internal data warehouses.
How does an OHLCV period boundary work?
An OHLCV period boundary works by defining a time window for each candle. A common convention is a half-open interval: the candle includes timestamps greater than or equal to the start time and strictly less than the end time.
For a candle from 10:00:00 to 10:01:00, trades at 10:00:00.000 belong to that candle, while trades at 10:01:00.000 belong to the next candle. This convention avoids overlap between adjacent candles.
What happens if OHLCV period boundaries are inconsistent?
If OHLCV period boundaries are inconsistent, candle values may not match across systems. A trade at the exact boundary may be assigned to different candles depending on the provider or implementation.
This can cause discrepancies in close prices, opening prices, volume totals, technical indicators, and strategy backtests. Boundary mismatches are often subtle but can become significant in high-frequency or high-volume markets.
How are OHLCV period boundaries used in crypto market data?
In crypto market data, OHLCV period boundaries are used to aggregate trades from continuously operating markets into standardized intervals. Because crypto markets trade 24/7, period boundaries are usually based on UTC timestamps rather than exchange sessions.
A data provider can use these boundaries to publish candles consistently across symbols, exchanges, and timeframes.
Real-World Example
Suppose a BTC/USD one-minute candle covers the period from 14:30:00 to 14:31:00 UTC. A trade at 14:30:59.900 is included in that candle. A trade at exactly 14:31:00.000 is included in the next candle.
If another system includes the 14:31:00.000 trade in the earlier candle, the two systems may report different close prices and volume values for both adjacent candles.
OHLCV Period Boundary and CoinAPI Market Data API
CoinAPI Market Data API provides access to standardized market data, including OHLCV candles across crypto exchanges and symbols. Understanding OHLCV period boundaries helps developers interpret candle timestamps correctly, align candles with raw trades, and avoid off-by-one-interval errors in analytics or trading systems.
When consuming OHLCV data, applications should treat candle timestamps and interval definitions consistently across historical backfills, real-time updates, and post-close reconciliation workflows.