CoinAPI

CoinAPI is an account-backed Provider that DataCat connects to directly from your Mac.

Provider access note: CoinAPI access is separate from a DataCat subscription. Use your own CoinAPI account and credentials.

What you need

You need your own CoinAPI account and an API credential accepted by CoinAPI. Credentials remain on your Mac and must not be placed in Job names, dataset paths, screenshots, or support messages.

CoinAPI tier

Select the CoinAPI tier that matches your current CoinAPI account. DataCat uses this setting to coordinate request pacing and concurrency; it is not a billing-plan selector or a usage estimate.

To find the value:

Sign in to CoinAPI Console.
Open Quotas and Limits.
Find your current CoinAPI Tier Program value, from Tier 0 through Tier 4, and select the matching value in the DataCat Provider configuration.

Do not confuse the CoinAPI Tier Program value with your monthly plan name or CoinAPI’s separate Tier 1 and Tier 2 WebSocket data categories. Usage estimates shown by DataCat describe the DataCat request plan; they are not exact CoinAPI billing.

Coverage model

CoinAPI provides crypto OHLCV across multiple supported venues and symbols. Available symbols, periods, history, quotas, and charges depend on the current CoinAPI account and provider terms.

DataCat retains the provider and venue identities in dataset provenance. Similar symbols from different venues or providers are not interchangeable records.

History and Live

History loads completed CoinAPI bars for the selected range. Live writes each newly completed bar as it becomes available. Open or in-progress updates are not written as completed Dataset bars. History + Live combines both flows in one Job without intentionally leaving a gap.

Technical details: REST and WebSocket

DataCat uses CoinAPI REST for History and WebSocket for primary Live delivery. History + Live establishes WebSocket coverage first and then runs the REST backfill. During a recoverable WebSocket interruption, REST fallback can cover subsequently closed periods without changing the visible Job mode.

Finality and recent bars

CoinAPI can revise recent OHLCV while historical consolidation is still in progress. The Provider Account’s configurable Finality delay determines when a recent completed period becomes due for REST confirmation.

According to CoinAPI guidance, OHLCV consolidation typically takes about 1–2 hours after a period closes. DataCat therefore uses 2 hours — Recommended as the default Finality delay. This is a practical waiting period, not a finality guarantee or SLA, and CoinAPI may still revise data later.

You can instead select 10 minutes, 30 minutes, 1 hour, 4 hours, or 8 hours in the CoinAPI Provider configuration. Shorter delays let DataCat confirm recent rows sooner but increase revision risk. Longer delays reduce that risk but keep recent rows in pending_finalization for longer.

Recent rows can therefore be stored with provider_data_status = pending_finalization. Eligible REST confirmation promotes a matching row to final; this is a DataCat durable-finality policy, not a guarantee that CoinAPI data can never change.

Zero-trade and missing rows

CoinAPI can return a real OHLCV row with zero trades and zero volume when its methodology derives prices from quote movement. DataCat preserves that provider row.

If CoinAPI returns no row, DataCat does not invent raw OHLCV. The dataset records the applicable pending, omitted, or provider-error state so downstream analysis can distinguish missing input from a real zero-volume period.

Account limits and terms

CoinAPI can apply credits, rate limits, concurrency limits, plan restrictions, availability rules, and additional fees. DataCat coordinates known limits but cannot observe requests made by other software using the same CoinAPI account.

Review the current CoinAPI terms and usage policy before collecting, retaining, or redistributing provider data.