Native IEX Admin Messages

Administrative and Market Status Messages from the IEX Exchange

Access historical administrative market messages published by IEX through FinFeedAPI. Retrieve trading status updates, official prices, auction information, operational halt notifications, short sale price test events, retail liquidity indicators, security directory messages, security events, and system events.

Native IEX Admin Messages preserve the original administrative messages distributed by the Investors Exchange, providing historical insight into market state changes and operational events that accompany trading activity.

Explore Documentation Get Your API Key

What Are Native IEX Admin Messages?

Native IEX Admin Messages are operational messages published by the Investors Exchange alongside market data. Rather than representing trades or quotes, these messages communicate changes in market status, trading conditions, auctions, security attributes, regulatory events, and exchange operations throughout the trading day.

Unlike Native IEX Trades, which capture completed executions, Admin Messages describe the market environment in which those executions occur. They indicate when securities begin or stop trading, when auctions are scheduled or completed, when official opening or closing prices are published, and when regulatory conditions such as short sale restrictions become active.

Unlike Level 1 Quotes, Level 2 Price Levels, or Level 3 Order Book events, which focus on market liquidity, Admin Messages provide contextual information that explains why market behavior may change during a trading session.

Because these messages are timestamped alongside the rest of the Native IEX feed, they help developers align price movements with the exact operational state of the exchange at that moment.

This makes them especially valuable for compliance review, market replay, anomaly detection, and post-trade analysis where understanding the surrounding market context matters as much as the trade or quote itself.

Developers frequently combine Admin Messages with trades, quotes, and order book data to reconstruct complete historical market conditions, identify auction periods, interpret trading halts, and analyze exchange-specific events.

What's Included?

Each response contains one or more administrative message types published by IEX during the requested trading day.

Message Type	What it means
trading_status	Indicates whether a security is trading live, halted, paused, or in an order acceptance period, together with the reason where available.
official_price	Publishes official opening or closing prices released by IEX.
security_event	Reports significant market events affecting a security, such as completion of opening or closing processes.
auction_information	Provides auction state, indicative clearing prices, imbalance information, paired shares, auction collars, and scheduled auction times.
short_sale_price_test	Indicates whether the Short Sale Price Test restriction is active and includes the associated status details.
operational_halt_status	Reports whether a security is operationally halted on IEX.
retail_liquidity_indicator	Identifies available retail buy or sell interest published by the exchange.
system_event	Reports exchange-wide operational events such as the start or end of market sessions and message distribution.
security_directory	Provides reference information about a security, including round lot size and LULD tier classification.

Together, these messages provide historical context surrounding trading activity, allowing developers to interpret market state transitions, regulatory events, auction processes, and operational conditions alongside executions and order book updates.

Available REST Endpoints

FinFeedAPI provides REST endpoints for retrieving historical Native IEX administrative messages for individual stock symbols. The same dataset is also available through JSON-RPC and the hosted FinFeedAPI MCP Server.

Get Admin Messages

Returns historical administrative messages published by IEX for a specific stock symbol on a selected trading day. If no date parameter is supplied, the latest available trading day is returned.

Response may include

trading status updates
official opening and closing prices
auction information and imbalance data
operational halt notifications
short sale price test status
retail liquidity indicators
security events
security directory information
system events

Requires an API key passed via the Authorization header. Accepts path parameter symbol (for example AAPL) and optional query parameter date formatted as YYYY-MM-DD (ISO 8601 UTC).

MCP & JSON-RPC Support

Native IEX Admin Messages are available through multiple protocol interfaces beyond the standard REST API.

MCP Server

The hosted FinFeedAPI Stock Historical MCP Server exposes Native IEX Admin Messages through the stock_native_iex_admin_messages tool. AI agents, LLMs, and MCP-compatible clients can retrieve historical administrative events using the standard X-APIKey header.

Typical workflow

1Discover supported exchanges using stock_exchanges_list.
2Retrieve available symbols with stock_symbols_list.
3Request administrative messages using stock_native_iex_admin_messages by supplying symbol, date, and an optional limit.

If no dataset exists for the selected symbol and trading date, the MCP server returns an explicit error rather than a partial response.

JSON-RPC

Developers using JSON-RPC can access Native IEX Admin Messages through the production endpoint at https://api-historical.stock.finfeedapi.com/jsonrpc.

JSON-RPC acts as a transport wrapper around the REST API. Requests specify method as v1/native/iex/admin/messages/{symbol} while passing symbol and date inside params. Authentication, parameters, and response structures remain identical to the REST interface.

Dataset Characteristics

Historical Native IEX administrative market messages
Available through REST API, JSON-RPC proxy, and hosted MCP Server
API key authentication required
Single-symbol retrieval per request
Optional trading date parameter (defaults to the latest available trading day)
ISO 8601 UTC timestamps
Nanosecond timestamp precision (timestamp_nanos)
Multiple administrative message types returned within a single response
Includes market status, auction, regulatory, operational, and reference information
Explicit error responses when no dataset exists for the requested symbol and trading date

Why Developers Use Native IEX Admin Messages

Administrative messages complement market data by describing the operational state of the exchange rather than executed transactions.

If you need...	Use...
Trading halt and market status history	Native IEX Admin Messages
Official opening and closing prices	Native IEX Admin Messages
Auction state, indicative prices, and imbalance information	Native IEX Admin Messages
Short sale restriction history	Native IEX Admin Messages
Retail liquidity indicators	Native IEX Admin Messages
Tick-level execution records	Native IEX Trades
Bid and ask quote updates	Native IEX Level 1 Quotes
Order book depth	Native IEX Level 2 Price Levels
Full order lifecycle events	Native IEX Level 3 Order Book

Many market surveillance, analytics, and quantitative research systems combine Admin Messages with trades and order book data to reconstruct complete historical market conditions.

Common Use Cases

Reconstruct historical trading session state
Detect trading halts and resumptions
Analyze opening and closing auction activity
Study official opening and closing prices
Track short sale restriction events
Interpret operational market events alongside executions
Enrich historical market replay and compliance workflows

Who Uses This Dataset?

Market Data Platforms
Quantitative Trading Firms
Market Surveillance Teams
Financial Analytics Providers
Academic Researchers

Native IEX Admin Messages

Explore Native IEX Admin Messages

Native IEX Admin Messages provide the operational context surrounding historical trading activity on the Investors Exchange. Together with trades, quotes, order books, metadata, OHLCV datasets, System Events, and the FinFeedAPI Stock Historical MCP Server, they help developers reconstruct historical market conditions with greater accuracy.