Native IEX System Events

System and Market Operational Events from the IEX Exchange

Access historical exchange-wide operational events directly from IEX through FinFeedAPI. Retrieve system state transitions, market boundary indicators, feed heartbeat triggers, nanosecond timestamps, and event code descriptions across our supported protocols.

Native IEX System Events preserve every operational state message published by IEX without aggregation or filtering, making them essential for market session tracking, algorithmic event alignment, exchange state monitoring, order-entry gate verification, and microstructural research.

Explore Documentation Get Your API Key

What Are Native IEX System Events?

Native IEX System Events represent exchange-wide operational and market session transitions generated by the Investors Exchange.

Unlike symbol-specific data streams (such as Trades or Quotes), which report activity for individual securities, system events signal macro state changes across the entire IEX platform. Each record details the specific event code, human-readable status text, precise timestamp, and dedicated boolean state flags indicating critical trading day milestones.

The Native IEX System Events dataset provides raw venue status messages exactly as disseminated by the IEX matching engine. It allows developers to track protocol heartbeats, detect the start and end of system communications, and establish precise boundaries for regular market trading hours.

Unlike Level 1 Quotes or Level 2 Price Levels, which reflect continuous pricing and liquidity changes, System Events define the operational container and session rules within which orders are submitted, processed, or restricted.

Unlike Level 3 Order Book or Trades data, which track order lifecycle and execution prints for individual assets, System Events provide global timestamp anchors for the whole trading venue.

Developers routinely combine Native IEX System Events with Admin Messages, Level 1 Quotes, Level 2 Price Levels, and Level 3 Order Books to synchronize data feeds, validate market session state, and ensure execution algorithms operate strictly within permitted trading windows.

FinFeedAPI exposes Native IEX System Events through a consistent historical REST API, JSON-RPC proxy, and MCP interface.

What's Included?

Each system event record describes a single exchange-wide state transition or system message on the IEX market.

Field	What it means
timestamp	UTC ISO 8601 timestamp when the system event occurred.
timestamp_nanos	Nanosecond-resolution integer timestamp for precise event sequencing.
system_event	Raw numerical identifier assigned to the system event by IEX.
system_event_code	Single-character code representing the system event type (e.g., "O", "S", "E").
system_event_text	Descriptive human-readable explanation of the operational state transition.
is_system_event_start_of_messages	Indicates whether the event signals the opening message feed of the session (true) or not (false).
is_system_event_start_of_system_hours	Indicates whether IEX system operations have begun for the day.
is_system_event_start_of_regular_market_hours	Indicates the official start of regular market trading hours (e.g., 09:30:00 EST).
is_system_event_end_of_regular_market_hours	Indicates the official close of regular market trading hours (e.g., 16:00:00 EST).
is_system_event_end_of_system_hours	Indicates whether IEX system operations have shut down for the day.
is_system_event_end_of_messages	Indicates whether the event signals the final message feed output of the session.

Together, these fields allow developers to align session timestamps, audit algorithmic execution start/stop boundaries, verify data feed integrity, and track IEX system state transitions down to the nanosecond.

Available REST Endpoints

FinFeedAPI provides REST endpoints for retrieving historical system operational events and market status transitions for the IEX exchange. For alternative transport protocols and AI-driven workflows, Native IEX System Events are also accessible through JSON-RPC and the hosted FinFeedAPI MCP Server.

Get System Events

Returns historical Native IEX system-wide operational events and market session transitions. The dataset contains session markers, feed boundaries, and state flags throughout a trading day. Requires a trading date parameter.

Response includes

system event code, numerical ID, and descriptive text
nanosecond timestamp and ISO 8601 UTC timestamp
complete session boundary boolean flags (start/end of messages, start/end of system hours, start/end of regular market hours)

Requires an API key passed via the Authorization header (or X-APIKey). Accepts query parameter date formatted as YYYY-MM-DD (or ISO 8601 UTC string).

MCP & JSON-RPC Support

Native IEX System Events are accessible through multiple protocol interfaces beyond standard REST.

MCP Server

The hosted FinFeedAPI Stock Historical MCP Server exposes Native IEX System Events as a self-describing tool (stock_native_iex_system_events), allowing AI agents, LLMs, and MCP-compatible clients (e.g., Cursor, Claude Desktop) to retrieve operational events using the X-APIKey header.

Discovery and query workflow

1Discover supported exchanges with stock_exchanges_list.
2Retrieve system events using stock_native_iex_system_events by providing the target date and an optional limit.

If no system event data exists for the selected trading date, the MCP server returns an explicit error message instead of a partial payload.

JSON-RPC

Developers using JSON-RPC can access Native IEX System Events via the production proxy.

JSON-RPC acts as a thin transport wrapper over the REST API. The request sets method to v1/native/iex/admin/system-event and passes date within params. The proxy forwards the request to the underlying REST endpoint while retaining identical authentication, parameters, and response structures.

Dataset Characteristics

Historical Native IEX exchange-wide operational system event data
Available through REST API, JSON-RPC proxy, and hosted MCP Server
API key authentication required (Authorization header, X-APIKey, or apikey parameter)
Venue-level retrieval requested by trading date
ISO 8601 UTC timestamp formatting
Nanosecond timestamp precision (timestamp_nanos)
Standardized event codes (system_event_code) paired with explanatory string details (system_event_text)
Comprehensive boolean indicators for system hours, regular market hours, and feed message boundaries
Explicit error responses for invalid or non-trading date requests

Why Developers Use Native IEX System Events Instead of Symbol-Level Data

Both datasets record venue activity, but they serve different operational purposes.

If you need...	Use...
Precise start and close markers for regular trading hours	Native IEX System Events
Verification of system initialization and feed start/stop boundaries	Native IEX System Events
Global timestamp synchronization across multi-feed pipelines	Native IEX System Events
Automated session gating for algorithmic order routers	Native IEX System Events
Auditing exchange-wide system operational state transitions	Native IEX System Events
Individual transaction execution details and trade break detection	Native IEX Trades
Order book depth tracking and individual bid/ask updates	Native IEX Level 2 / Level 3
Aggregated OHLCV price trend analysis over multi-day windows	OHLCV Historical Data

Many production systems combine both datasets. Quantitative applications often utilize Native IEX System Events to establish global time anchors and gate trading logic at system open, shifting to Native IEX Trades, Order Books, or OHLCV series for security-specific trading strategies during active session hours.

Common Use Cases

Synchronize data ingest pipelines using explicit start-of-messages and end-of-messages markers
Audit algorithmic trading bots to guarantee orders are submitted strictly within permitted system hours
Reconstruct full-day market replay simulations aligned with official exchange session transitions
Measure latencies between system open triggers and first liquidity prints
Validate market-wide circuit breaker state changes and operational session boundaries

Who Uses This Dataset?

Quantitative Trading & Infrastructure Teams
Exchange Data Feed Architects
Financial Analytics Platforms
AI and Algorithmic Trading Systems
Compliance & Market Surveillance Teams

Native IEX System Events

Explore Native IEX System Events Data

Native IEX System Events supply venue-level operational state changes direct from the Investors Exchange, delivering the global timestamp precision and session boundary details required for feed synchronization, algorithmic gating, and market infrastructure monitoring.

The dataset integrates naturally with the broader FinFeedAPI Stock ecosystem, including Metadata endpoints for venue lookup, Native IEX Trades, Level 1 Quotes, Level 2 Price Levels, Level 3 Order Books, Admin Messages, OHLCV timeseries datasets, and the hosted Stock Historical MCP Server.