Feeds / US options

Nasdaq Options Top of Market (ISE, GEMX, MRX, PHLX, BX)

Nasdaq ISE, GEMX, MRX, PHLX and BX options exchanges. Top of book (best bid and offer) per option series.

Handler built · validated on exchange dataUS Options

Venues covered (5): Nasdaq ISE, Nasdaq GEMX, Nasdaq MRX, Nasdaq PHLX, Nasdaq BX Options

Protocol

Venue
Nasdaq ISE, GEMX, MRX, PHLX and BX options exchanges
Asset class
US Options
Wire format
Options Top of Market 2.1: big-endian binary messages over MoldUDP64 multicast, one format shared by the five Nasdaq options exchanges; the exchange's best bid and offer per option series, with customer and professional-customer sizes. SoupBinTCP is used for replay only.
Messages
System Event, Derivative Directory, Trading Action, Best Bid AND Ask Update (short / long), Best Bid OR Ask Update (short / long), End of Replay Sequence
Book
Top of book (best bid and offer) per option series
Sequencing
MoldUDP64 sequence per channel; A/B duplicates skipped; gaps reported. Glimpse snapshot recovery code is present but incomplete and untested.
Validation
Validated 2026-11-20 in our production handler framework (MD) on Nasdaq's public sample captures for ISE, GEMX and MRX (November 2025) and PHLX (December 2025): 20 captures, 6.1 million messages. Against a decoder we wrote independently from the 2.1 specification, every option series' quote sequence was identical (4.05 million quote states), with zero errors. BX Options uses the same format but has no 2.1 sample. Exchange-direct input: our production handler does not yet take live UDP multicast, so this handler runs on captures in our test tools today; live multicast input and gap recovery are in development.

Notes

Official documentation

Options Top of Market feed specification v2.1 ↗www.nasdaq.comOptions Top of Market Glimpse specification ↗www.nasdaq.comNasdaq options specifications and resources ↗www.nasdaq.com

Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.

Interested?

This handler is not running in our public stack. It is built for clients with their own exchange connectivity and licences; live multicast input is in development.

Talk to us