Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.4Field

NoMDEntryTypes <267>

Tag
267
Type
NumInGroup (base int)
FIXML name
NoMDEntryTyps
Pedigree
Added FIX 4.2
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows NoMDEntryTypes <267> as defined in FIX 4.4. For the current standard, see tag 267 NoMDEntryTypes in FIX Latest.

NoMDEntryTypes <267> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

NoMDEntryTypes counts the MDEntryType (269) values requested on a Market Data Request.

Where it is used

MDReqGrp (repeating group) . In all, 1 message in FIX 4.4 can carry it. Full list.

Example message

8=FIX.4.4|9=120|35=V|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|262=MDR-1|263=1|264=1|265=1|267=2|269=0|269=1|146=1|55=AAPL|10=028

Illustrative example, not real orders or market data. A MarketDataRequest (35=V) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.

Related tags: MDEntryType <269>

Description (from the Orchestra file)

Number of MDEntryType (269) fields requested.

Used in

Components and repeating groups (1)

NameKindPresence
MDReqGrpRepeating groupNumInGroup
All 1 messages that can carry NoMDEntryTypes, including through components and groups