Specify
Pin venue, spot or derivatives market, native symbols, interval, time range, and dataset cutoff.
Historical crypto data
Historical crypto prices built for reproducible backtesting
Define venue, market type, symbols, interval, UTC range, and cutoff. DataCedar preserves raw source objects, normalized bars, catalog history, and coverage evidence so later backfills do not silently rewrite the experiment.
30.8M+
validated one-minute rows
1376
initial spot pairs
UTC
interval clock
Immutable
raw source objects
Definition
Historical crypto data is a series of past observations tied to a venue and instrument. Backtest-ready history also retains symbol status, listing boundaries, units, continuous expected intervals, gaps, source runs, and a fixed information cutoff.
How DataCedar handles it01 02 03 04
What you can query, which fields are returned, and how availability is reported.
Backfill
Verify archive objects and reconcile their boundary with recent REST or live observations.
Validate
Check expected intervals, OHLC relationships, duplicates, listing boundaries, and source row counts.
Freeze
Save the query, catalog snapshot, schema, raw manifest, and gap report beside the model result.
Data surface
What the schema is built to carry.
One-minute OHLCV schema
Venue and market identity
UTC interval boundaries
Listing and status history
Expected-versus-actual counts
Raw archive checksums
Deterministic dataset cutoffs
CSV and Parquet-ready records
Product boundary: The 4,662,588,748-row production corpus covers 3,649 archive-eligible Spot-family instruments. Public serving is active, while complete cold history for every active and inactive pair is still deepening.
API example
Historical spot bars
GET /v3/crypto/{symbol}/bars
Request
curl "https://api.datacedar.com/v3/crypto/ETHUSDT/bars?timeframe=1Min&start=2024-01-01T00:00:00Z&end=2024-01-02T00:00:00Z"Representative response
{
"data": [],
"coverage": {
"stored_rows": true,
"status": "served",
"public_serving": true
}
}Examples document the public contract and may use illustrative values or redacted identifiers. Availability fields and rights filters are authoritative for the active environment.
Research workflow
Four steps from API key to a validated dataset.
01
Define
Fix market, symbols, UTC range, interval, and cutoff.
02
Audit
Compare archive manifests and normalized row counts.
03
Reject gaps
Fail closed on unexplained missing intervals or mappings.
04
Snapshot
Version the data and validation evidence together.
Field guide
Constructing backtest-ready crypto history
01
A ticker is not an instrument key
The same display ticker can refer to different venues or product types. Store venue, native symbol, base, quote or settlement asset, and product class.
Historical universes must retain symbols that later delist, expire, or change status.
02
Continuous coverage changes gap logic
Crypto commonly trades through weekends. Expected intervals should begin at listing and make maintenance, suspension, and collection outages explicit.
Never replace a missing candle with zero volume without evidence.
03
Separate observations from fills
OHLCV does not reveal intrabar ordering, queue position, spread, or achievable size. Backtests must add fees, slippage, funding, and venue execution rules separately.
Save those assumptions with the frozen data snapshot.
Comparison
Historical download versus a reproducible crypto dataset
A file of candles is only the observation layer; a defensible experiment also needs identity, coverage, lineage, and a cutoff.
CriterionTypical latest-value feedDataCedar research model
Venue scopeOften hidden behind a symbol listVenue and market type remain explicit
Missing intervalsEmpty rows or silent forward fillsExpected, actual, and gap state recorded
Instrument identityDisplay ticker used as the keyNative symbol plus versioned canonical identity
Source dependencyCustomer request calls the upstream APIOwned raw storage and normalized serving tables
AvailabilityEndpoint presence implies coverageCoverage and rights state fail closed
Before you rely on it
A practical validation checklist.
- 01The venue and market type are named for every instrument
- 02First and last available timestamps are reported by stream
- 03UTC interval, event-time, and receive-time rules are documented
- 04Delisted, expired, pending, and suspended instruments remain visible
- 05Archive, REST, and live boundaries have been reconciled
- 06Duplicate, sequence, and expected-interval checks pass
- 07The intended display or redistribution use is explicitly permitted
Questions, answered.
The July 26, 2026 build snapshot contains 4,662,588,748 distinct one-minute Binance spot candles across 3,649 archive-eligible Spot-family instruments.
Continue the research
Crypto market data API →
Evaluate one-minute crypto OHLCV, symbols, and coverage through a venue-explicit, independently stored, rights-aware data model.
Binance historical data →
Understand and evaluate Binance historical archives, spot symbols, one-minute OHLCV, backfill reconciliation, and independent storage.
Crypto derivatives data →
Model crypto perpetuals and futures with contract identity, mark and index prices, funding, open interest, liquidations, expiries, history, and gaps.
Tokenized stock data →
Research tokenized and equity-linked crypto products with explicit instrument type, venue, underlying mapping, trading status, reference methodology, and rights.