Price charts show the outcome. Deeper historical data can help analysts investigate the trading activity, liquidity conditions, and market events surrounding those movements.
FinFeedAPI provides T+1 historical OHLCV and market metadata across 40+ exchanges, with detailed Native IEX historical microstructure data for supported symbols and dates. Analysts can combine price history with supported trades, quotes, order book events, and exchange-level context to investigate historical market activity from multiple perspectives.
Charts and technical indicators are useful for identifying historical patterns, trends, volatility, and momentum.
But aggregated price data removes much of the activity within each period. Analysts looking only at candles may have limited information about spreads, displayed liquidity, individual trades, order book activity, or changes in exchange state.
OHLCV shows historical price and volume but compresses the activity that occurred within each period.
Volume alone does not show where displayed liquidity was available across the order book.
An indicator may identify an unusual period without explaining what trades, quotes, or order book changes occurred around it.
Session transitions, auctions, halts, and trading-status changes can affect how historical observations should be interpreted.
Moving beyond OHLCV often requires trade, quote, order book, and event-level information that needs to be aligned correctly.
Suppose a stock moves sharply during a particular historical period.
OHLCV can show the magnitude and direction of that move. A deeper investigation might ask:
These additional observations do not automatically establish why a price moved. They give analysts more historical evidence to investigate what was happening around it.
FinFeedAPI provides T+1 historical OHLCV across 40+ exchanges through a standardized interface. For analyses that require deeper exchange-level detail, supported Native IEX historical datasets add trades, Level 1 quotes, Level 2 price levels, Level 3 order book events, system events, and administrative messages.
Native IEX Level 1 provides historical best bid, best ask, and associated sizes. Analysts can use these observations to study spread behavior and top-of-book conditions around historical price movements or signals.
Native IEX Level 2 provides displayed liquidity across multiple price levels. This allows researchers to examine how visible depth was distributed and how it changed during selected historical periods.
Native IEX Level 3 provides individual historical order book lifecycle events. Analysts can study supported order additions, modifications, deletions, executions, and book-clearing activity to investigate how the displayed book evolved over time.
Native IEX system events provide information including system hours, regular market hours, message boundaries, and session-state transitions. Administrative messages add symbol-level context including trading status, auctions, operational halts, official open/close prices, and other relevant events.
REST and JSON-RPC provide structured access to historical Stock API resources. Analysts can define symbols, dates, periods, and datasets consistently across recurring research and analytical workflows.
Start with a period of unusual price or volume activity and examine the supported historical trades, quotes, liquidity, and exchange events around it. This adds additional evidence to the price chart without assuming a single cause for the movement.
Native IEX Level 1 data can be used to examine how the bid-ask spread changed during selected periods. Analysts can compare spread conditions across different market environments or around specific historical events.
Native IEX Level 2 allows analysts to study displayed liquidity across multiple price levels. This can support research into depth distribution, liquidity concentration, and changes in the visible book.
Native IEX Level 3 events can be used to investigate how individual order events contributed to changes in the displayed book. Researchers can examine additions, modifications, deletions, executions, and book-clearing activity around periods of interest.
System events and administrative messages can help analysts distinguish regular market hours from other exchange states and identify supported auctions, halts, or trading-status changes. This provides additional context when comparing observations across historical periods.
Analysts can calculate a signal from OHLCV and then examine supported Native IEX data around the same period. This makes it possible to study how price-based observations relate to spreads, trades, displayed depth, and order book activity.
Broad historical OHLCV can provide the starting point for market analysis, while supported Native IEX datasets allow deeper investigation of exchange-level activity.
| Data | What It Provides | How It Can Support Analysis |
|---|---|---|
| OHLCV | T+1 historical open, high, low, close, and volume across 40+ exchanges | Trends, returns, volatility, volume, technical analysis, and historical comparisons |
| Market Metadata | Exchange and symbol information | Instrument discovery and consistent organization of analytical datasets |
| Trades | Individual historical trades and supported condition flags | Trade-level investigation, filtering, and activity analysis |
| Level 1 | Historical best bid, best ask, and associated sizes | Spread and top-of-book analysis |
| Level 2 | Displayed liquidity across price levels | Depth, liquidity-distribution, and visible-book analysis |
| Level 3 | Individual order book lifecycle events | Detailed order-flow and book-evolution research |
| System Events | System hours, regular market hours, message boundaries, and session-state transitions | Session segmentation and exchange-state context |
| Administrative Messages | Trading status, auctions, operational halts, official open/close prices, and other symbol-level information | Context around unusual periods and symbol-level events |
OHLCV and market metadata provide the broadest foundation for market analysis. Trades, Level 1, Level 2, Level 3, system events, and administrative messages described here are Native IEX historical datasets for supported symbols and dates.
| What the Analysis Needs | Before | With FinFeedAPI |
|---|---|---|
| Historical price analysis | Analysis may rely primarily on charts and aggregated price series | T+1 historical OHLCV provides standardized price and volume observations across 40+ exchanges |
| Trade-level context | Individual trading activity may not be visible | Native IEX trades provide transaction-level observations and supported condition flags |
| Spread analysis | Historical spreads may be unavailable or approximated | Native IEX Level 1 provides historical bid/ask observations |
| Liquidity analysis | Liquidity may be inferred mainly from price and volume | Native IEX Level 2 provides displayed liquidity across price levels |
| Order book analysis | Individual book activity is unavailable in OHLCV | Native IEX Level 3 provides historical order book lifecycle events |
| Market timing | Different trading periods may be analyzed without exchange-state context | System events provide additional historical session context |
| Unusual periods | Auctions, halts, or status changes may require separate investigation | Administrative messages provide supported symbol-level event context |
| Repeatable research | Analysis may depend on multiple datasets and custom retrieval processes | Structured API access supports consistently defined historical workflows |
FinFeedAPI provides structured interfaces for retrieving historical stock data for research, analytics, dashboards, and automated analysis.
REST works well for research scripts, notebooks, dashboards, analytical applications, and scheduled historical data retrieval.
Analysts can request supported data for defined symbols and periods and process it within their own analytical environment.
JSON-RPC provides structured RPC-based access for supported historical stock workflows.
It can be integrated into automated analytics, research infrastructure, and applications that repeatedly query historical market data.
FinFeedAPI also provides a hosted Stock Historical MCP server.
Supported tools for exchange and symbol discovery, OHLCV, and Native IEX historical resources can be used in compatible AI-assisted research and analytical workflows.
A chart might show:
A deeper analysis can continue:
The result is not an automatic explanation of causality. It is a richer historical evidence set that analysts can use to investigate the movement.
Start with T+1 historical OHLCV and add trade, spread, liquidity, order book, and exchange-state information when your analysis requires deeper context.
FinFeedAPI provides historical OHLCV across 40+ exchanges, market metadata, and detailed Native IEX historical datasets where supported, giving analysts a structured foundation for historical market research and deeper exchange-level investigation.
