Stock market data API

Stock data API for filings, fundamentals, earnings, news, and historical OHLCV

Use one API key and 18 REST routes to query assets, permitted bars, SEC filings, filing text, XBRL facts, earnings events, stock-news links, macro observations, coverage, and ingestion health.

Start free Read the API docs
v3
stable REST namespace
18
implemented research routes
Cursor
deterministic pagination
Fail closed
rights-aware serving
Definition

A stock market data API gives software structured access to equity information. DataCedar focuses on historical and event-driven research rather than quote screens: market observations, filings, facts, schedules, documents, news references, and macro series use one stable interface.

How DataCedar handles it

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

01

Start from a symbol

Resolve the security once, then query bars, filings, documents, facts, earnings events, news references, transcripts, coverage, and short-volume status through consistent routes.

02

Treat availability as data

Health and coverage responses separate complete, partial, missing, stale, unavailable, and rights-restricted streams instead of returning an ambiguous empty array.

03

Filter by what was known

As-of queries exclude later schedule changes, amendments, and fact revisions so the returned information set matches the simulated decision time.

04

Own the serving layer

Sources are isolated to acquisition. DataCedar preserves raw inputs, normalizes stable tables, authenticates keys, meters plans, and serves the downstream contract independently.

Data surface

What the schema is built to carry.

Security master and symbol search
Historical OHLCV when permitted
SEC filings and document text
Point-in-time XBRL fundamentals
Versioned earnings events
Public news-link metadata
Macroeconomic observations
Coverage and ingestion health

Product boundary: The initial product does not redistribute consolidated real-time SIP quotes or trades. Quote and trade routes remain unavailable until a separately licensed source grants the required serving rights.

API example

Company evidence timeline

GET /v3/stocks/{symbol}/events
Request
curl "https://api.datacedar.com/v3/stocks/AAPL/events?as_of=2026-07-01T20:00:00Z&limit=50" \
  -H "Authorization: Bearer $QUARTERTRACE_API_KEY"
Representative response
{
  "data": [{
    "event_type": "sec_filing",
    "symbol": "AAPL",
    "effective_at": "2026-05-01T20:05:00Z",
    "known_at": "2026-05-01T20:05:00Z",
    "source": "sec_edgar",
    "source_id": "accession:..."
  }],
  "pagination": { "has_more": false },
  "meta": { "request_id": "..." }
}

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

Resolve

Search the security master and retain the canonical identity rather than joining solely on today's ticker.

02

Query

Choose one stream or request the event timeline at a precise as-of cutoff.

03

Verify

Read pagination, coverage, source, and rights metadata before accepting the sample.

04

Join

Connect events and observations with stable symbol, issuer, fiscal-period, and time keys.

Field guide

Choosing a stock market data API for research

01

Match the API to the job

A trading interface optimizes for the newest quote and low latency. A historical research interface optimizes for stable identifiers, revision history, deterministic pagination, source inspection, and repeatable snapshots. Those are different products.

DataCedar deliberately prioritizes the second job. It lets a researcher move from a market reaction to the filing, event, fundamental fact, or news reference that was available at that moment.

  • Use a licensed live feed for execution or display.
  • Use point-in-time evidence for historical simulation.
  • Do not infer redistribution rights from technical access.
02

An empty response needs a reason

An empty list may mean no event occurred, the collector failed, the source was not yet covered, the account lacks entitlement, or the row cannot be served. Returning those outcomes as the same shape pushes hidden data-quality errors into customer code.

DataCedar keeps a coverage ledger and ingestion run status so clients can fail closed, retry a transient problem, or document a known limitation.

  • Check stream coverage before batch jobs.
  • Persist request IDs for support and audits.
  • Page with cursors instead of unstable offsets.
03

Source independence starts after acquisition

Provider-neutral does not mean source-free. It means a source adapter cannot control canonical identifiers, normalized tables, access policies, or the public API contract.

Raw responses land in immutable object storage first. Normalizers and the serving API are ours, so a permitted replacement source can be onboarded without redesigning every customer integration.

  • Keep source IDs and retrieval runs.
  • Version normalized schemas.
  • Apply rights filters at serving time as well as ingestion time.
Comparison

Quote API versus research API

The right choice depends on whether the application acts now or reconstructs then.

Primary objectiveLatest price with low latencyReproducible historical evidence
Time modelObservation timestampEffective, published, retrieved, and known-at
CorrectionsLatest value winsNew version with lineage
Missing dataEmpty or provider-specificExplicit coverage state
Linked contextSeparate products and identifiersFilings, facts, events, news, and macro
Before you rely on it

A practical validation checklist.

  1. 01The API's license covers your display and redistribution use
  2. 02The symbol model survives ticker changes
  3. 03Pagination is stable for backfills
  4. 04Every stream exposes a known-at or publication time
  5. 05Corrections do not overwrite prior evidence
  6. 06Coverage can distinguish absent from unavailable
  7. 07Rate and history limits are compatible with the batch size

Questions, answered.

No. The launch product is a historical and point-in-time research API, not a consolidated real-time SIP service.

Continue the research

Historical stock data →

Build historical stock price and volume exports with explicit adjustments, coverage checks, symbol history, and event windows for reproducible backtesting.

SEC filings API →

Query SEC filing metadata, primary documents, exhibits, XBRL facts, and amendments with accession-level provenance and known-at timestamps.

Earnings calendar API →

Query scheduled, confirmed, rescheduled, and completed earnings events with known-at history, source evidence, fiscal periods, and reaction windows.

Earnings call transcripts API →

A searchable, event-linked earnings-call schema for licensed transcripts and permitted issuer audio, with speakers, sections, source provenance, and rights controls.

Create a free API key for filings, facts, earnings events, news links, and macro data.

Explorer is $0 with no card and a 1 request/second limit. Market history and transcript text appear only when an eligible source is active for the account.

Open DataCedar