When you pull OHLCV (Open, High, Low, Close, Volume) data from CoinAPI, the numbers may not match exactly what you see on Binance, Coinbase, or TradingView. This can be confusing for beginners, but it’s normal. Here’s why, and how to use the data correctly.

1. Understanding the Source of Discrepancies

A. Different Data Providers

CoinAPI aggregates data from hundreds of crypto exchanges, normalizing and standardizing it into a unified format.

However:

• Exchanges/TradingView often use internal (native) order book and trade data, sometimes filtered or processed differently.
• CoinAPI receives data via public APIs or data feeds, sometimes with latency, rate limits, or different sampling resolutions.

B. Differences in Time Intervals

• TradingView often builds candles using server-side aggregation, which may differ in:
  • Time zone (UTC vs exchange time)
  • Precision (e.g. milliseconds vs seconds)
  • Volume filters
• CoinAPI candles are aggregated by:
  • Trade data timestamps
  • Consistent UTC-based intervals

This leads to slight differences in OHLCV values, especially for fast-moving or low-liquidity markets.

C. Precision Rounding

• CoinAPI applies standardized decimal precision across instruments.
• Exchanges may expose more (or fewer) decimal places for prices or volumes.
• CoinAPI simplifies some precision metadata for uniformity across markets.

🔧 You can still access native exchange metadata using CoinAPI's /instruments or /symbols endpoints to get precision values per market.

2. Why OHLCV Data May Appear Incomplete

Common causes:

Solutions:

• Use the period_id parameter (e.g. 1MIN, 1HRS) carefully when calling /ohlcv/latest or /ohlcv/history.
• Check your subscription plan for historical data depth.
• Enable data fallbacks or interpolate gaps in your frontend/charting logic.

3. Tips for Developers Using CoinAPI

A. Get OHLCV Data:

1GET /v1/ohlcv/{symbol_id}/history

Example:

1GET /v1/ohlcv/BITSTAMP_SPOT_BTC_USD/history?period_id=1MIN&limit=100

B. Get Instrument Precision:

1GET /v1/instruments

Use this to retrieve metadata like:

• price_precision
• volume_precision
• min_trade_size

C. Sample Python Snippet:

1import requests
2
3headers = {'X-CoinAPI-Key': 'YOUR_API_KEY'}
4url = '<https://rest.coinapi.io/v1/ohlcv/BINANCE_SPOT_BTC_USDT/history>'
5params = {
6    'period_id': '1MIN',
7    'time_start': '2023-01-01T00:00:00',
8    'limit': 100
9}
10
11response = requests.get(url, headers=headers, params=params)
12ohlcv_data = response.json()
13print(ohlcv_data)

4. Summary

Further Reading

• CoinAPI Docs – OHLCV Endpoint
• CoinAPI Docs – Instrument Metadata

Pro Tip

Always align your application’s timezone, data frequency, and instrument metadata with CoinAPI’s standardized format when comparing against third-party platforms. Use CoinAPI data for consistency and automation, but don’t expect pixel-perfect parity with visual platforms like TradingView.