Stock market datasets

Stock market datasets built for reproducible research

Choose the stock data your model actually needs: historical OHLCV, a security master, SEC filings and documents, point-in-time company facts, earnings events, source-linked news, macro observations, and dataset coverage. DataCedar exposes these streams through one versioned API so a buyer can test the schema, rights, history, and missing-data behavior before committing engineering time.

8 streams
market and company evidence
2 clocks
effective and known-at time
1 schema
versioned API contract
Explicit
coverage and source rights
Definition

A stock market dataset is more than a table of prices. A research-ready dataset identifies the security behind each symbol, states which sessions and records should exist, separates effective time from when information became knowable, preserves source lineage, and reports whether absent data is empty, delayed, partial, restricted, or missing.

How DataCedar handles it

What you can query, which fields are returned, and how availability is reported.

01

Historical stock price and volume data

Query source-labeled OHLCV by symbol, interval, and elapsed date range. Keep raw and adjusted views distinguishable, retain the market session key, and inspect expected-versus-actual coverage before using the series in a backtest, chart, feature store, or model.

02

Security identity and symbol history

Resolve a current or historical ticker to a canonical security record before joining datasets. Issuer identity, listing attributes, ticker changes, and delisted states prevent the current-symbol shortcut from corrupting a historical universe.

03

SEC filings, documents, and fundamentals

Join filing chronology, accession metadata, primary documents, exhibits, and SEC/XBRL company facts to the same security identity. Accepted timestamps and known-at filters preserve the information set available at a historical decision time.

04

Earnings, news, events, and macro context

Add earnings dates, company events, public news references, and macro observations without flattening every timestamp into one date. Citations, revisions, source rights, and coverage state remain inspectable beside the normalized record.

Data surface

What the schema is built to carry.

Daily and rolling intraday stock OHLCV
Security master and historical symbol resolution
SEC filing chronology and accession metadata
Permitted filing documents and exhibits
Point-in-time SEC/XBRL company facts
Earnings calendar and company-event history
Source-linked company news metadata
Macroeconomic observations
Expected-versus-actual coverage records
Raw-source identifiers, retrieval time, and rights class

Product boundary: DataCedar is not a consolidated real-time exchange feed and does not promise unrestricted redistribution of every upstream field. Available history, latency, text access, and export rights depend on the dataset and plan. Coverage responses expose those limits so buyers can reject an unsuitable stream before production use.

API example

Discover the stock universe before requesting data

GET /v3/stocks/assets
Request
curl "https://api.datacedar.com/v3/stocks/assets?q=AAPL&status=active&limit=10" \
  -H "X-API-Key: $DATACEDAR_API_KEY"
Representative response
{
  "data": [{
    "symbol": "AAPL",
    "name": "Apple Inc.",
    "asset_class": "stock",
    "status": "active",
    "source": "sec_nasdaq_security_master"
  }],
  "coverage": {
    "status": "available",
    "checked_at": "2026-07-31T00:00:00Z"
  },
  "pagination": { "next_cursor": null }
}

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

Write down the target universe, history window, bar interval, adjustment policy, evidence streams, known-at rule, and acceptable missing-data threshold.

02

Inspect

Test the security catalog and coverage endpoints first. Confirm available symbols, earliest eligible history, latency, rights, and partial states before downloading rows.

03

Join

Use canonical security identity and explicit timestamps to connect bars with filings, facts, earnings, news references, events, and macro observations.

04

Freeze

Save the query, cutoff, cursor, schema version, coverage response, and source identifiers beside the model artifact so the run can be investigated and repeated.

Field guide

How to buy a stock market dataset without importing hidden bias

01

Start with the research decision, not the largest row count

A large dataset can still be unusable if it omits delisted securities, rewrites historical fundamentals with the latest restatement, or cannot explain a missing session. Define the decision the data must support and the historical information boundary before comparing vendor totals.

For price research, specify the universe, exchange calendar, interval, adjustment view, and corporate-action treatment. For event research, specify which filings, earnings records, news references, or macro series must be observable by a given known-at cutoff. These requirements turn a vague data purchase into a testable acceptance plan.

  • List required and optional fields separately.
  • Define the earliest and latest eligible timestamps.
  • State whether corrections may rewrite prior exports.
  • Set a maximum unexplained-gap rate before evaluation.
02

Audit identity, time, coverage, and rights as first-class fields

Ticker strings are not permanent identities. Mergers, relistings, share classes, symbol reuse, and delistings all create false joins when a dataset keys history only by the symbol visible today. A security master should resolve the issuer and listing represented by every market row.

Time needs the same discipline. An earnings period, filing acceptance, publication time, retrieval time, and dataset known-at time answer different questions. Coverage and rights are also data: an empty array caused by an unavailable source must not look like a verified absence, and a retrievable field must not be assumed redistributable.

  • Resolve symbols before joining independent streams.
  • Preserve effective, publication, accepted, and known-at time.
  • Distinguish empty, partial, stale, restricted, and unavailable states.
  • Confirm export and downstream display rights for the intended use.
03

Run a paid-use acceptance test before migration

Test the provider with ordinary symbols, thinly traded names, a ticker change, a delisted case, a split window, a filing amendment, and a known period with market holidays. Compare expected records with returned records and require the API to explain material differences.

Then run the exact downstream path: pagination, retries, incremental updates, a frozen historical query, and an export into the storage or model format you will operate. Measure engineering effort as well as subscription price. A cheap feed that needs a second identity vendor and extensive gap repair can be the expensive choice.

  • Save representative requests and responses as contract fixtures.
  • Verify pagination is stable and resumable.
  • Re-run one frozen query to test reproducibility.
  • Document plan limits, overages, latency, support, and cancellation terms.
Comparison

Stock market dataset purchase criteria

Price is only one line in the decision. The durable choice is the dataset that makes its historical and operational boundaries testable.

UniverseCurrent tickers with unclear survivorshipSecurity identity, status, and symbol history remain explicit
HistoryA start date without expected coverageAvailable range and expected-versus-actual state are queryable
TimeOne timestamp reused for every meaningEffective, accepted, published, retrieved, and known-at roles stay distinct
CorrectionsLatest values silently replace historySource records, retrieval runs, and revisions remain traceable
Missing dataEmpty response treated as no eventEmpty, partial, stale, restricted, and unavailable states differ
RightsAccess assumed to imply redistributionSource and serving-rights class accompany the dataset
IntegrationSeparate identifiers and incompatible envelopesOne security namespace and versioned response contract
Before you rely on it

A practical validation checklist.

  1. 01The dataset covers the securities and historical period in the research plan
  2. 02Delisted securities, share classes, and ticker changes are testable
  3. 03Raw and adjusted price behavior is documented
  4. 04Trading sessions, timezones, and intraday interval rules are explicit
  5. 05Filings and fundamentals retain accession and accepted-time lineage
  6. 06Earnings and news records support a historical known-at cutoff
  7. 07Missing, partial, stale, restricted, and empty results are distinguishable
  8. 08Pagination, rate limits, latency, and plan entitlements fit production volume
  9. 09Export and downstream display rights match the intended product
  10. 10A frozen sample query can be repeated with its coverage evidence

Questions, answered.

DataCedar exposes stock OHLCV, a security master, SEC filings and permitted documents, point-in-time SEC/XBRL facts, earnings events, company-event history, source-linked news metadata, macro observations, and coverage records through one API.

Test the stock datasets against your real acceptance criteria.

Create a free key, inspect the universe and coverage state, and run representative stock, filing, fundamental, earnings, and news queries before you buy.

Start free