Common Issues

Connection issues

My API key is rejected or I see an authentication error

Double-check that you copied the full API key from your Coin API dashboard with no leading or trailing spaces. Free-tier keys are valid but have usage restrictions — if your key has expired or exceeded its quota, generate a new one from your account settings.

The data flow fails immediately after setup

This usually means the Symbol ID is invalid or formatted incorrectly. Symbol IDs are case-sensitive and exchange-specific (e.g., BITSTAMP_SPOT_BTC_USD). Check the Coin API symbol list to confirm the exact ID for your trading pair.

Missing data

My data flow returns zero rows

Check three things: (1) The Symbol ID exists and has data for your selected date range. (2) Your start and end dates are set correctly using the date pickers — a reversed date range will return nothing. (3) Your record limit isn't set to 0. The default is 100, so if you've accidentally entered 0, no records will be returned.

Data stops before my specified end date

You've likely hit the record limit cap. The maximum is 100,000 records per request. If your combination of symbol, interval, and date range produces more records than the limit allows, the pull will stop early. Narrow your date range or use a larger time interval (e.g., switch from 1-minute to 1-hour candles) to reduce the row count.

Some time periods have gaps in OHLCV data

Gaps usually reflect periods of no trading activity on that specific exchange for that symbol. This is expected behavior — Coin API only records candles where trades actually occurred. If you need a gap-filled series, you'll need to handle that downstream in your destination (e.g., in BigQuery or a spreadsheet formula).

Permission errors

I get a 403 error when pulling historical data

Free-tier Coin API accounts have restricted access to historical data — typically limited to the past 30 days. A 403 on historical requests usually means your plan doesn't cover that date range. Upgrade your Coin API subscription or adjust your start date to fall within your plan's allowed window.

Data discrepancies

Prices don't match what I see on a trading exchange's website

Coin API aggregates data from specific exchange feeds. Make sure your Symbol ID matches the exact exchange you want (e.g., BINANCE_SPOT_BTC_USDT vs. COINBASE_SPOT_BTC_USD). Price differences between exchanges are normal due to arbitrage gaps and liquidity differences.

Rate limits

My data flow is throttled or returns rate limit errors

Coin API enforces rate limits based on your subscription tier. If you're running multiple data flows against the same API key simultaneously, requests can stack up and trigger throttling. Stagger your data flow schedules or reduce the number of concurrent flows. If you consistently hit limits, consider upgrading your Coin API plan.