What is included in historical stock data api?

symbol and stable security ID, session or bar timestamp, open, high, low, close, volume, raw or adjusted view, source and retrieval time, coverage status. Coverage is reported by security, interval, and elapsed session. Missing, partial, unavailable, and rights-restricted states remain distinct from a legitimate zero.

Can I use this for historical backtesting?

Yes, where coverage and serving rights permit it. Save the query, source, known-at cutoff, schema version, and coverage result with the experiment.

Prices dataset

Historical stock data API

Q: Where does DataCedar get prices data?

Permitted market-history sources. DataCedar serves only market history whose source terms permit the requested use. Validation-only Alpaca SIP records never flow into the public serving layer.

Request historical bars programmatically with date, interval, adjustment, limit, and cursor controls.

Start with the API Read the API docs

Primary source

Permitted market-history sources

API route

/v3/stocks/{symbol}/bars

Coverage

Explicit by stream

Serving

Rights-aware

What this dataset means

Historical stock-price data records how a security traded during past market sessions. Research-grade history needs more than open, high, low, and close: it must identify the security through ticker changes, state the exchange calendar and timezone, distinguish raw from adjusted prices, and disclose which expected sessions are missing.

The buyer’s objective is straightforward: Integrate reproducible price history into a product or research pipeline. DataCedar keeps the research contract visible so the output can be inspected before it is trusted.

Fields delivered

symbol and stable security ID

session or bar timestamp

open, high, low, close

volume

raw or adjusted view

source and retrieval time

coverage status

The endpoint is /v3/stocks/{symbol}/bars. Responses retain deterministic pagination and the metadata needed to connect normalized records to their source run.

How to evaluate a provider

Evaluate pagination stability, rate limits, correction policy, coverage responses, and redistribution rights—not only the sample JSON.

DataCedar is not a consolidated real-time SIP feed. Use a separately licensed real-time source for execution, quote display, or low-latency decisions. DataCedar deliberately exposes that boundary in the product rather than leaving customers to infer it from a missing endpoint or a legal footnote.

Failure modes to test before purchase

Unstable cursors.
Ambiguous empty arrays.
Technical access confused with serving rights.
Acquisition access is treated as proof of redistribution rights.
An empty array cannot distinguish no event from incomplete collection.

Source, freshness, and reproducibility

Source. Permitted market-history sources. DataCedar stores source identifiers and retrieval runs before normalization, then serves its own stable downstream schema.

Freshness. Completed historical sessions are filled proactively after the market closes, then checked against the expected exchange calendar before they become available.

Rights. DataCedar serves only market history whose source terms permit the requested use. Validation-only Alpaca SIP records never flow into the public serving layer.

Questions, answered.

The research schema includes symbol and stable security ID, session or bar timestamp, open, high, low, close, volume, raw or adjusted view, source and retrieval time, coverage status. Fields remain connected to source, retrieval, coverage, and rights metadata.