What is included in stock trading volume history?

symbol and security ID, interval start and end, trading session, reported share volume, price fields for alignment, coverage state, source rights class. Volume shares the bar key used by price data. The coverage ledger identifies absent bars and partial sessions rather than filling them with 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.

Volume dataset

Stock trading volume history

Q: Where does DataCedar get volume data?

Permitted historical market sources. Public responses are restricted to sources and plans that permit downstream serving; acquisition credentials are never the public data contract.

Analyze how reported share volume changed across trading sessions and company events.

Start with the API Read the API docs

Primary source

Permitted historical market sources

API route

/v3/stocks/{symbol}/bars?fields=timestamp,volume

Coverage

Explicit by stream

Serving

Rights-aware

What this dataset means

Stock volume is the number of shares reported as traded during a defined interval. It is meaningful only with a market, session, interval, and source: daily consolidated volume, venue volume, and an intraday bar are not interchangeable measurements.

The buyer’s objective is straightforward: Build volume-event windows or liquidity filters from historical observations. DataCedar keeps the research contract visible so the output can be inspected before it is trusted.

Fields delivered

symbol and security ID

interval start and end

trading session

reported share volume

price fields for alignment

coverage state

source rights class

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

How to evaluate a provider

Join volume to the exact price interval and exchange calendar; use known-at event times so an after-hours filing belongs to the next tradable session.

Volume from a free chart endpoint may differ from consolidated SIP volume. DataCedar labels the source and does not imply consolidated real-time coverage. 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

Calendar-day joins.
Premarket and regular hours mixed.
Corporate actions ignored.
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 historical market sources. DataCedar stores source identifiers and retrieval runs before normalization, then serves its own stable downstream schema.

Freshness. Elapsed sessions are checked after close and can be reprocessed when the upstream source publishes a correction.

Rights. Public responses are restricted to sources and plans that permit downstream serving; acquisition credentials are never the public data contract.

Questions, answered.

The research schema includes symbol and security ID, interval start and end, trading session, reported share volume, price fields for alignment, coverage state, source rights class. Fields remain connected to source, retrieval, coverage, and rights metadata.