How to View Historical Candlestick Data on Binance

Accessing Candlestick Data via Binance Web Interface

1. Navigate to the Binance spot trading page and select a specific trading pair such as BTC/USDT.

2. Locate the chart area and click the time interval dropdown—options include 1m, 5m, 15m, 1h, 4h, 1d, 1w, and 1M.

3. Right-click on the chart canvas to open the context menu and choose “Export data” to download CSV files containing open, high, low, close, volume, and timestamp fields.

4. Adjust the visible chart range by dragging horizontally or using the zoom slider at the bottom of the chart widget.

5. Hover over any candle to view precise OHLCV values and UTC timestamp in a tooltip.

Retrieving Historical Data Through Binance REST API

1. Construct a GET request to https://api.binance.com/api/v3/klines with mandatory parameters: symbol (e.g., ETHUSDT), interval (e.g., 1h), and optional startTime/endTime in milliseconds.

2. The response returns an array of 12-element arrays, where each sub-array encodes open time, open price, high, low, close, volume, close time, quote asset volume, number of trades, taker buy base volume, taker buy quote volume, and ignore field.

3. Use the limit parameter to control batch size—maximum allowed is 1000; pagination requires adjusting startTime to the last close time plus one millisecond.

4. Handle rate limits: 1200 requests per minute for public endpoints; exceedance triggers HTTP 429 with Retry-After header.

5. Validate timestamps against server time obtained from /api/v3/time to prevent skew-induced gaps or overlaps in fetched intervals.

Using Binance Cryptocurrency MCP for AI Agents

1. Integrate the Model Context Protocol service into agent frameworks like Claude or Cursor to issue natural-language queries about candlestick patterns.

2. Submit prompts such as “Show me the 4-hour candlestick data for SOL/USDT from October 1 to October 10, 2026” and receive structured JSON responses with full kline arrays.

3. Leverage built-in time window normalization—queries specifying “last 30 days” automatically resolve to correct Unix epoch boundaries aligned with UTC midnight.

4. Cross-validate output against raw API results when debugging divergence in candle aggregation logic or timezone interpretation.

5. Parse the “isFinal” boolean flag in responses to distinguish finalized candles from provisional ones still subject to exchange-side adjustments.

Data Integrity and Timestamp Considerations

1. All candlestick timestamps reflect the start time of the interval—not end time—so a 1d candle labeled “2026-10-15” begins at 00:00:00 UTC and ends at 23:59:59.999 UTC.

2. Missing candles occur only during exchange maintenance windows or infrastructure failures—not due to low liquidity—and are never interpolated by Binance servers.

3. Volume values represent base asset volume only; quote asset volume must be derived separately using close price multiplication if needed.

4. Server-side candle generation uses exchange-maintained order matching timestamps, not ingestion timestamps, ensuring consistency across all data channels.

5. Timezone-aware clients must convert local time inputs to UTC before submitting API requests, as Binance does not perform automatic timezone translation.

Frequently Asked Questions

Q: Can I fetch candlestick data older than 1 year via the public API?Yes. The /api/v3/klines endpoint serves historical data from the listing date of each symbol. BTC/USDT supports data since July 2017; newer pairs like PEPE/USDT begin from their launch date.

Q: Why do exported CSV files sometimes show fewer rows than expected for a given date range?This occurs when the selected time interval exceeds the available trading history for that pair. For example, requesting 1w candles for a token launched 10 days ago yields only one row.

Q: Does Binance adjust historical candles after trade cancellations or corrections?No. Finalized candles are immutable once written. Only real-time candles marked “provisional” may change before finalization; those changes are reflected in subsequent API calls with updated isFinal status.

Q: Is there a way to detect gaps in candle continuity without manual inspection?Compare sequential closeTime values. A gap exists if the next candle’s openTime exceeds the current candle’s closeTime + interval duration. Scripts can automate this validation across large batches.